This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-13 16:06
Elapsed34m32s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 500 lines ...
I0613 16:12:55.898943   11881 up.go:43] Cleaning up any leaked resources from previous cluster
I0613 16:12:55.898958   11881 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
I0613 16:12:55.915614   11887 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 16:12:55.915710   11887 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0613 16:12:56.434577   11881 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0613 16:12:56.434618   11881 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
I0613 16:12:56.450260   11897 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 16:12:56.450482   11897 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0613 16:12:56.939753   11881 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/13 16:12:56 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
I0613 16:12:56.949079   11881 http.go:37] curl https://ip.jsb.workers.dev
I0613 16:12:57.089561   11881 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.184.77.158/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I0613 16:12:57.103687   11913 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 16:12:57.103771   11913 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0613 16:12:57.150611   11913 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0613 16:12:57.665581   11913 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0613 16:13:21.197659   11881 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
I0613 16:13:21.212496   11936 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 16:13:21.212580   11936 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0613 16:13:22.184397   11936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0613 16:14:32.481771   11936 validate_cluster.go:221] (will retry): cluster not yet healthy
W0613 16:14:42.516286   11936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 13 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 13 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 12 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-p7fhj		system-cluster-critical pod "cert-manager-5d46c5dc5b-p7fhj" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 9 lines ...
Machine	i-0fb12f0c3872fc21c					machine "i-0fb12f0c3872fc21c" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-7hxwv	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7hxwv" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-bvms4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-bvms4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-ccmpj		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-ccmpj" is pending

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

... skipping 15 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc			system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-node-9nktx						system-node-critical pod "ebs-csi-node-9nktx" is pending
Pod	kube-system/ebs-csi-node-s8rnc						system-node-critical pod "ebs-csi-node-s8rnc" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-132.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-132.ca-central-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-52-62.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-62.ca-central-1.compute.internal" is pending

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

... skipping 18 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc			system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is pending
Pod	kube-system/ebs-csi-node-4sd95						system-node-critical pod "ebs-csi-node-4sd95" is pending
Pod	kube-system/ebs-csi-node-v69hp						system-node-critical pod "ebs-csi-node-v69hp" is pending
Pod	kube-system/kube-proxy-ip-172-20-52-220.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-220.ca-central-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-54-27.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-27.ca-central-1.compute.internal" is pending

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

... skipping 12 lines ...
Pod	kube-system/calico-node-kgn2h				system-node-critical pod "calico-node-kgn2h" is not ready (calico-node)
Pod	kube-system/calico-node-phwjk				system-node-critical pod "calico-node-phwjk" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-lm7wc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-lm7wc" is not ready (cert-manager)
Pod	kube-system/ebs-csi-node-4sd95				system-node-critical pod "ebs-csi-node-4sd95" is pending
Pod	kube-system/ebs-csi-node-v69hp				system-node-critical pod "ebs-csi-node-v69hp" is pending

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-7fh8d	system-node-critical pod "calico-node-7fh8d" is not ready (calico-node)
Pod	kube-system/calico-node-kgn2h	system-node-critical pod "calico-node-kgn2h" is not ready (calico-node)
Pod	kube-system/calico-node-phwjk	system-node-critical pod "calico-node-phwjk" is not ready (calico-node)

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

... skipping 66 lines ...
ip-172-20-59-146.ca-central-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-f45c4bf76-mt7t9	system-cluster-critical pod "coredns-f45c4bf76-mt7t9" is pending

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 370 lines ...
Jun 13 16:27:26.700: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 58 lines ...
Jun 13 16:27:25.857: INFO: Creating resource for dynamic PV
Jun 13 16:27:25.857: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6722-e2e-scjld6v
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 13 16:27:25.979: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 16:27:26.045: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:28.108: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:30.108: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:32.108: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:34.110: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:36.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:38.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:40.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:42.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:44.114: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:46.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:48.108: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:50.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:52.109: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:54.108: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:56.110: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6722-e2e-scjld6v",
  	... // 2 identical fields
  }

Jun 13 16:27:56.174: INFO: Error updating pvc ebs.csi.aws.commgwfz: PersistentVolumeClaim "ebs.csi.aws.commgwfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 122 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:27:25.717: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:27:28.052: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 16:27:28.468: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0d458b1c235e63b8a".
Jun 13 16:27:28.468: INFO: Creating resource for pre-provisioned PV
Jun 13 16:27:28.468: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun 13 16:27:36.909: INFO: PersistentVolumeClaim pvc-v4f5m found but phase is Pending instead of Bound.
Jun 13 16:27:38.940: INFO: PersistentVolumeClaim pvc-v4f5m found but phase is Pending instead of Bound.
Jun 13 16:27:40.971: INFO: PersistentVolumeClaim pvc-v4f5m found and phase=Bound (12.220487971s)
Jun 13 16:27:40.971: INFO: Waiting up to 3m0s for PersistentVolume aws-t9n24 to have phase Bound
Jun 13 16:27:41.002: INFO: PersistentVolume aws-t9n24 found and phase=Bound (30.706937ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:27:43.189: INFO: Deleting pod "pod-26f1f141-f625-4ba5-8c4f-7e8bf81da40b" in namespace "volumemode-2023"
Jun 13 16:27:43.221: INFO: Wait up to 5m0s for pod "pod-26f1f141-f625-4ba5-8c4f-7e8bf81da40b" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 16:27:47.286: INFO: Deleting PersistentVolumeClaim "pvc-v4f5m"
Jun 13 16:27:47.319: INFO: Deleting PersistentVolume "aws-t9n24"
Jun 13 16:27:47.473: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0d458b1c235e63b8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d458b1c235e63b8a is currently attached to i-0fb12f0c3872fc21c
	status code: 400, request id: cb320aa5-1a93-4a28-a44b-3a9b2ad3afec
Jun 13 16:27:52.726: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0d458b1c235e63b8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d458b1c235e63b8a is currently attached to i-0fb12f0c3872fc21c
	status code: 400, request id: ab4f15e0-fa4e-4ce2-b556-72ea0976bd06
Jun 13 16:27:57.984: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0d458b1c235e63b8a".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:27:57.984: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2023" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 16:27:58.052: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 45 lines ...
Jun 13 16:27:29.795: INFO: Creating resource for dynamic PV
Jun 13 16:27:29.795: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4202htfb9
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 13 16:27:29.889: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 16:27:29.954: INFO: Error updating pvc awsv5jcw: PersistentVolumeClaim "awsv5jcw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4202htfb9",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 13 16:28:00.084: INFO: Error updating pvc awsv5jcw: PersistentVolumeClaim "awsv5jcw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 59 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 197 lines ...
Jun 13 16:27:27.877: INFO: Creating resource for dynamic PV
Jun 13 16:27:27.877: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3595pfgbg
STEP: creating a claim
Jun 13 16:27:27.911: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3595
Jun 13 16:27:28.013: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3595" in namespace "provisioning-3595" to be "Succeeded or Failed"
Jun 13 16:27:28.046: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 33.611363ms
Jun 13 16:27:30.078: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065652979s
Jun 13 16:27:32.110: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097059101s
Jun 13 16:27:34.143: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129823234s
Jun 13 16:27:36.175: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162253754s
Jun 13 16:27:38.208: INFO: Pod "volume-prep-provisioning-3595": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194928995s
Jun 13 16:27:40.239: INFO: Pod "volume-prep-provisioning-3595": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.226680745s
STEP: Saw pod success
Jun 13 16:27:40.240: INFO: Pod "volume-prep-provisioning-3595" satisfied condition "Succeeded or Failed"
Jun 13 16:27:40.240: INFO: Deleting pod "volume-prep-provisioning-3595" in namespace "provisioning-3595"
Jun 13 16:27:40.276: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3595" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-qlp5
STEP: Checking for subpath error in container status
Jun 13 16:27:46.411: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlp5" in namespace "provisioning-3595"
Jun 13 16:27:46.448: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qlp5" to be fully deleted
STEP: Deleting pod
Jun 13 16:27:46.480: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlp5" in namespace "provisioning-3595"
STEP: Deleting pvc
Jun 13 16:27:46.574: INFO: Deleting PersistentVolumeClaim "awshbsbt"
... skipping 37 lines ...
Jun 13 16:27:25.499: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-702jsmx8
STEP: creating a claim
Jun 13 16:27:25.609: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-v67q
STEP: Creating a pod to test exec-volume-test
Jun 13 16:27:25.763: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-v67q" in namespace "volume-702" to be "Succeeded or Failed"
Jun 13 16:27:25.805: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 41.889507ms
Jun 13 16:27:27.837: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073617662s
Jun 13 16:27:29.873: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109863259s
Jun 13 16:27:31.905: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.142251057s
Jun 13 16:27:33.945: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.182360962s
Jun 13 16:27:35.977: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.214245843s
... skipping 5 lines ...
Jun 13 16:27:48.181: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 22.41839869s
Jun 13 16:27:50.213: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 24.449991764s
Jun 13 16:27:52.246: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 26.482842533s
Jun 13 16:27:54.277: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Pending", Reason="", readiness=false. Elapsed: 28.514422055s
Jun 13 16:27:56.311: INFO: Pod "exec-volume-test-dynamicpv-v67q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.547551932s
STEP: Saw pod success
Jun 13 16:27:56.311: INFO: Pod "exec-volume-test-dynamicpv-v67q" satisfied condition "Succeeded or Failed"
Jun 13 16:27:56.343: INFO: Trying to get logs from node ip-172-20-52-220.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-v67q container exec-container-dynamicpv-v67q: <nil>
STEP: delete the pod
Jun 13 16:27:57.212: INFO: Waiting for pod exec-volume-test-dynamicpv-v67q to disappear
Jun 13 16:27:57.243: INFO: Pod exec-volume-test-dynamicpv-v67q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-v67q
Jun 13 16:27:57.243: INFO: Deleting pod "exec-volume-test-dynamicpv-v67q" in namespace "volume-702"
... skipping 87 lines ...
Jun 13 16:27:39.508: INFO: PersistentVolumeClaim pvc-qkpzs found but phase is Pending instead of Bound.
Jun 13 16:27:41.540: INFO: PersistentVolumeClaim pvc-qkpzs found and phase=Bound (12.228296825s)
Jun 13 16:27:41.540: INFO: Waiting up to 3m0s for PersistentVolume aws-nzxg5 to have phase Bound
Jun 13 16:27:41.571: INFO: PersistentVolume aws-nzxg5 found and phase=Bound (31.253134ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-2954
STEP: Creating a pod to test exec-volume-test
Jun 13 16:27:41.667: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-2954" in namespace "volume-2563" to be "Succeeded or Failed"
Jun 13 16:27:41.698: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 31.185688ms
Jun 13 16:27:43.731: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064087391s
Jun 13 16:27:45.764: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096655612s
Jun 13 16:27:47.796: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12903761s
Jun 13 16:27:49.828: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160633045s
Jun 13 16:27:51.862: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 10.195058545s
Jun 13 16:27:53.897: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Pending", Reason="", readiness=false. Elapsed: 12.230355263s
Jun 13 16:27:55.933: INFO: Pod "exec-volume-test-preprovisionedpv-2954": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.265935567s
STEP: Saw pod success
Jun 13 16:27:55.933: INFO: Pod "exec-volume-test-preprovisionedpv-2954" satisfied condition "Succeeded or Failed"
Jun 13 16:27:55.964: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-2954 container exec-container-preprovisionedpv-2954: <nil>
STEP: delete the pod
Jun 13 16:27:56.051: INFO: Waiting for pod exec-volume-test-preprovisionedpv-2954 to disappear
Jun 13 16:27:56.082: INFO: Pod exec-volume-test-preprovisionedpv-2954 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-2954
Jun 13 16:27:56.082: INFO: Deleting pod "exec-volume-test-preprovisionedpv-2954" in namespace "volume-2563"
STEP: Deleting pv and pvc
Jun 13 16:27:56.113: INFO: Deleting PersistentVolumeClaim "pvc-qkpzs"
Jun 13 16:27:56.145: INFO: Deleting PersistentVolume "aws-nzxg5"
Jun 13 16:27:56.312: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0037dc945173bf12e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0037dc945173bf12e is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: ee595511-ccee-4e33-861d-3bed2a795517
Jun 13 16:28:01.568: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0037dc945173bf12e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0037dc945173bf12e is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 6807d724-9d61-43e6-bf16-344c29864f4c
Jun 13 16:28:06.824: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0037dc945173bf12e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0037dc945173bf12e is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 3a757220-e49d-4f82-bd02-fbc4836c63a1
Jun 13 16:28:12.085: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0037dc945173bf12e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0037dc945173bf12e is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: ae06a359-cb13-4737-bfe2-2b8af2f168c0
Jun 13 16:28:17.351: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0037dc945173bf12e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0037dc945173bf12e is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 00788bb1-86ff-469e-8729-03d8400cde65
Jun 13 16:28:22.607: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0037dc945173bf12e".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:28:22.607: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2563" for this suite.
... skipping 68 lines ...

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

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

    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:27:27.434: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 13 16:27:29.310: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:27:29.310: INFO: Creating resource for dynamic PV
Jun 13 16:27:29.310: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5816j2bld
STEP: creating a claim
Jun 13 16:27:29.341: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mcxp
STEP: Checking for subpath error in container status
Jun 13 16:27:57.502: INFO: Deleting pod "pod-subpath-test-dynamicpv-mcxp" in namespace "provisioning-5816"
Jun 13 16:27:57.539: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mcxp" to be fully deleted
STEP: Deleting pod
Jun 13 16:28:07.603: INFO: Deleting pod "pod-subpath-test-dynamicpv-mcxp" in namespace "provisioning-5816"
STEP: Deleting pvc
Jun 13 16:28:07.694: INFO: Deleting PersistentVolumeClaim "aws9b8p8"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [sig-storage] Volume FStype [Feature:vsphere]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:28:27.993: INFO: >>> kubeConfig: /root/.kube/config
... skipping 48 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 48 lines ...
STEP: Creating a kubernetes client
Jun 13 16:27:25.370: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0613 16:27:26.415750   25952 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 13 16:27:26.415: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 13 16:27:26.477: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:27:26.477: INFO: Creating resource for dynamic PV
Jun 13 16:27:26.477: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-49429x98
STEP: creating a claim
Jun 13 16:27:26.509: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-95br
STEP: Checking for subpath error in container status
Jun 13 16:28:00.684: INFO: Deleting pod "pod-subpath-test-dynamicpv-95br" in namespace "provisioning-494"
Jun 13 16:28:00.716: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-95br" to be fully deleted
STEP: Deleting pod
Jun 13 16:28:08.781: INFO: Deleting pod "pod-subpath-test-dynamicpv-95br" in namespace "provisioning-494"
STEP: Deleting pvc
Jun 13 16:28:08.875: INFO: Deleting PersistentVolumeClaim "awsn7vqn"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 9 lines ...
Jun 13 16:27:26.928: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4414-e2e-sclw6lm
STEP: creating a claim
Jun 13 16:27:26.960: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l5pv
STEP: Creating a pod to test subpath
Jun 13 16:27:27.058: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l5pv" in namespace "provisioning-4414" to be "Succeeded or Failed"
Jun 13 16:27:27.090: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.286948ms
Jun 13 16:27:29.122: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063995383s
Jun 13 16:27:31.155: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096750787s
Jun 13 16:27:33.187: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128638968s
Jun 13 16:27:35.219: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160341707s
Jun 13 16:27:37.252: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193551021s
... skipping 6 lines ...
Jun 13 16:27:51.482: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 24.424024831s
Jun 13 16:27:53.519: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.460165146s
Jun 13 16:27:55.551: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 28.492136305s
Jun 13 16:27:57.582: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.523894311s
Jun 13 16:27:59.614: INFO: Pod "pod-subpath-test-dynamicpv-l5pv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.555987413s
STEP: Saw pod success
Jun 13 16:27:59.615: INFO: Pod "pod-subpath-test-dynamicpv-l5pv" satisfied condition "Succeeded or Failed"
Jun 13 16:27:59.646: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-l5pv container test-container-volume-dynamicpv-l5pv: <nil>
STEP: delete the pod
Jun 13 16:27:59.717: INFO: Waiting for pod pod-subpath-test-dynamicpv-l5pv to disappear
Jun 13 16:27:59.748: INFO: Pod pod-subpath-test-dynamicpv-l5pv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l5pv
Jun 13 16:27:59.748: INFO: Deleting pod "pod-subpath-test-dynamicpv-l5pv" in namespace "provisioning-4414"
... skipping 454 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 185 lines ...
Jun 13 16:27:58.211: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6051ckppq
STEP: creating a claim
Jun 13 16:27:58.243: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rfd7
STEP: Creating a pod to test subpath
Jun 13 16:27:58.337: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rfd7" in namespace "provisioning-6051" to be "Succeeded or Failed"
Jun 13 16:27:58.368: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.613975ms
Jun 13 16:28:00.399: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062193114s
Jun 13 16:28:02.431: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093438839s
Jun 13 16:28:04.463: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1253413s
Jun 13 16:28:06.495: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158149822s
Jun 13 16:28:08.526: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188975397s
Jun 13 16:28:10.558: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220694259s
Jun 13 16:28:12.589: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.251736968s
Jun 13 16:28:14.621: INFO: Pod "pod-subpath-test-dynamicpv-rfd7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.283916672s
STEP: Saw pod success
Jun 13 16:28:14.621: INFO: Pod "pod-subpath-test-dynamicpv-rfd7" satisfied condition "Succeeded or Failed"
Jun 13 16:28:14.652: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-rfd7 container test-container-subpath-dynamicpv-rfd7: <nil>
STEP: delete the pod
Jun 13 16:28:14.723: INFO: Waiting for pod pod-subpath-test-dynamicpv-rfd7 to disappear
Jun 13 16:28:14.756: INFO: Pod pod-subpath-test-dynamicpv-rfd7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rfd7
Jun 13 16:28:14.756: INFO: Deleting pod "pod-subpath-test-dynamicpv-rfd7" in namespace "provisioning-6051"
... skipping 110 lines ...
Jun 13 16:27:25.414: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8374-e2e-scg9lnp
STEP: creating a claim
Jun 13 16:27:25.460: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sx6k
STEP: Creating a pod to test atomic-volume-subpath
Jun 13 16:27:25.705: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sx6k" in namespace "provisioning-8374" to be "Succeeded or Failed"
Jun 13 16:27:25.758: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 53.083385ms
Jun 13 16:27:27.790: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085012713s
Jun 13 16:27:29.823: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117696871s
Jun 13 16:27:31.855: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.150474197s
Jun 13 16:27:33.889: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.184532114s
Jun 13 16:27:35.922: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216940954s
... skipping 12 lines ...
Jun 13 16:28:02.351: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Running", Reason="", readiness=true. Elapsed: 36.645842932s
Jun 13 16:28:04.383: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Running", Reason="", readiness=true. Elapsed: 38.677978493s
Jun 13 16:28:06.418: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Running", Reason="", readiness=true. Elapsed: 40.713048666s
Jun 13 16:28:08.452: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Running", Reason="", readiness=true. Elapsed: 42.747062496s
Jun 13 16:28:10.484: INFO: Pod "pod-subpath-test-dynamicpv-sx6k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.779019189s
STEP: Saw pod success
Jun 13 16:28:10.484: INFO: Pod "pod-subpath-test-dynamicpv-sx6k" satisfied condition "Succeeded or Failed"
Jun 13 16:28:10.516: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-sx6k container test-container-subpath-dynamicpv-sx6k: <nil>
STEP: delete the pod
Jun 13 16:28:10.602: INFO: Waiting for pod pod-subpath-test-dynamicpv-sx6k to disappear
Jun 13 16:28:10.634: INFO: Pod pod-subpath-test-dynamicpv-sx6k no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sx6k
Jun 13 16:28:10.634: INFO: Deleting pod "pod-subpath-test-dynamicpv-sx6k" in namespace "provisioning-8374"
... skipping 291 lines ...
Jun 13 16:27:25.673: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8726-e2e-scwl9kj      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-8726    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-8726-e2e-scwl9kj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8726    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-8726-e2e-scwl9kj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8726    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-8726-e2e-scwl9kj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8726-e2e-scwl9kj    e6f19b8c-2d54-4d5e-bc36-1ba4a87a1839 2767 0 2021-06-13 16:27:25 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-13 16:27:25 +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-qzntb pvc- provisioning-8726  097a247b-a0c1-400e-a86d-5b70f17cc986 2792 0 2021-06-13 16:27:25 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-13 16:27:25 +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-8726-e2e-scwl9kj,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-709d785a-214e-4d40-a428-a6047a5e6424 in namespace provisioning-8726
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 13 16:27:48.117: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-pw4kv" in namespace "provisioning-8726" to be "Succeeded or Failed"
Jun 13 16:27:48.147: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.359741ms
Jun 13 16:27:50.179: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062093371s
Jun 13 16:27:52.210: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093262398s
Jun 13 16:27:54.242: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124859419s
Jun 13 16:27:56.273: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155867708s
Jun 13 16:27:58.303: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186576164s
... skipping 7 lines ...
Jun 13 16:28:14.560: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.44304816s
Jun 13 16:28:16.594: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 28.477212404s
Jun 13 16:28:18.626: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.509006293s
Jun 13 16:28:20.657: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Pending", Reason="", readiness=false. Elapsed: 32.540562234s
Jun 13 16:28:22.688: INFO: Pod "pvc-volume-tester-writer-pw4kv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.571322959s
STEP: Saw pod success
Jun 13 16:28:22.688: INFO: Pod "pvc-volume-tester-writer-pw4kv" satisfied condition "Succeeded or Failed"
Jun 13 16:28:22.757: INFO: Pod pvc-volume-tester-writer-pw4kv has the following logs: 
Jun 13 16:28:22.757: INFO: Deleting pod "pvc-volume-tester-writer-pw4kv" in namespace "provisioning-8726"
Jun 13 16:28:22.795: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-pw4kv" 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-40-132.ca-central-1.compute.internal"
Jun 13 16:28:22.922: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-kc782" in namespace "provisioning-8726" to be "Succeeded or Failed"
Jun 13 16:28:22.953: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Pending", Reason="", readiness=false. Elapsed: 31.507053ms
Jun 13 16:28:24.985: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062881544s
Jun 13 16:28:27.017: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095213613s
Jun 13 16:28:29.049: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127587556s
Jun 13 16:28:31.080: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158367253s
Jun 13 16:28:33.111: INFO: Pod "pvc-volume-tester-reader-kc782": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.189448742s
STEP: Saw pod success
Jun 13 16:28:33.111: INFO: Pod "pvc-volume-tester-reader-kc782" satisfied condition "Succeeded or Failed"
Jun 13 16:28:33.177: INFO: Pod pvc-volume-tester-reader-kc782 has the following logs: hello world

Jun 13 16:28:33.177: INFO: Deleting pod "pvc-volume-tester-reader-kc782" in namespace "provisioning-8726"
Jun 13 16:28:33.212: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-kc782" to be fully deleted
Jun 13 16:28:33.242: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qzntb] to have phase Bound
Jun 13 16:28:33.274: INFO: PersistentVolumeClaim pvc-qzntb found and phase=Bound (32.081401ms)
... skipping 468 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:28:50.003: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:28:50.157: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:28:50.157: INFO: Creating resource for dynamic PV
Jun 13 16:28:50.157: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1309wfgdx
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:28:56.380: INFO: Deleting pod "pod-d9ccbc97-cfbe-4c1f-99f1-356e5709c6cd" in namespace "volumemode-1309"
Jun 13 16:28:56.412: INFO: Wait up to 5m0s for pod "pod-d9ccbc97-cfbe-4c1f-99f1-356e5709c6cd" to be fully deleted
STEP: Deleting pvc
Jun 13 16:29:00.534: INFO: Deleting PersistentVolumeClaim "awsbq4zv"
Jun 13 16:29:00.565: INFO: Waiting up to 5m0s for PersistentVolume pvc-381f30e6-e902-4bf5-88d9-b5171a43203e to get deleted
Jun 13 16:29:00.595: INFO: PersistentVolume pvc-381f30e6-e902-4bf5-88d9-b5171a43203e found and phase=Released (30.37038ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 16:29:15.807: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 51 lines ...
Jun 13 16:28:36.386: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3744-e2e-scnl2lp
STEP: creating a claim
Jun 13 16:28:36.424: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tpz7
STEP: Creating a pod to test multi_subpath
Jun 13 16:28:36.526: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tpz7" in namespace "provisioning-3744" to be "Succeeded or Failed"
Jun 13 16:28:36.558: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 31.800431ms
Jun 13 16:28:38.593: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066300019s
Jun 13 16:28:40.628: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101868232s
Jun 13 16:28:42.663: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13667426s
Jun 13 16:28:44.696: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169311995s
Jun 13 16:28:46.730: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.203720013s
Jun 13 16:28:48.761: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.235243439s
Jun 13 16:28:50.793: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.266933779s
Jun 13 16:28:52.825: INFO: Pod "pod-subpath-test-dynamicpv-tpz7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.298457847s
STEP: Saw pod success
Jun 13 16:28:52.825: INFO: Pod "pod-subpath-test-dynamicpv-tpz7" satisfied condition "Succeeded or Failed"
Jun 13 16:28:52.857: INFO: Trying to get logs from node ip-172-20-40-132.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-tpz7 container test-container-subpath-dynamicpv-tpz7: <nil>
STEP: delete the pod
Jun 13 16:28:52.935: INFO: Waiting for pod pod-subpath-test-dynamicpv-tpz7 to disappear
Jun 13 16:28:52.966: INFO: Pod pod-subpath-test-dynamicpv-tpz7 no longer exists
STEP: Deleting pod
Jun 13 16:28:52.966: INFO: Deleting pod "pod-subpath-test-dynamicpv-tpz7" in namespace "provisioning-3744"
... skipping 28 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:28:42.604: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:28:42.763: INFO: Creating resource for dynamic PV
Jun 13 16:28:42.764: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6587-e2e-scpfc68
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:28:48.995: INFO: Deleting pod "pod-bd8576ea-a0f5-40b1-bbe8-b114efbb5ba8" in namespace "volumemode-6587"
Jun 13 16:28:49.027: INFO: Wait up to 5m0s for pod "pod-bd8576ea-a0f5-40b1-bbe8-b114efbb5ba8" to be fully deleted
STEP: Deleting pvc
Jun 13 16:28:59.150: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comh6tmw"
Jun 13 16:28:59.181: INFO: Waiting up to 5m0s for PersistentVolume pvc-a8b0d98c-0061-452f-9957-e42500d0a9de to get deleted
Jun 13 16:28:59.213: INFO: PersistentVolume pvc-a8b0d98c-0061-452f-9957-e42500d0a9de found and phase=Released (32.175935ms)
... skipping 13 lines ...

• [SLOW TEST:51.930 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 68 lines ...
Jun 13 16:28:45.388: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4743-e2e-scczs7t
STEP: creating a claim
Jun 13 16:28:45.420: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4fnt
STEP: Creating a pod to test subpath
Jun 13 16:28:45.516: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4fnt" in namespace "provisioning-4743" to be "Succeeded or Failed"
Jun 13 16:28:45.546: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 30.692105ms
Jun 13 16:28:47.579: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063631046s
Jun 13 16:28:49.611: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095105906s
Jun 13 16:28:51.642: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126144667s
Jun 13 16:28:53.675: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159035014s
Jun 13 16:28:55.707: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191407427s
Jun 13 16:28:57.738: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.222627009s
Jun 13 16:28:59.770: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.25446508s
Jun 13 16:29:01.802: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.286444458s
Jun 13 16:29:03.834: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.318329412s
Jun 13 16:29:05.866: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.350710662s
Jun 13 16:29:07.898: INFO: Pod "pod-subpath-test-dynamicpv-4fnt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.381949787s
STEP: Saw pod success
Jun 13 16:29:07.898: INFO: Pod "pod-subpath-test-dynamicpv-4fnt" satisfied condition "Succeeded or Failed"
Jun 13 16:29:07.928: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-4fnt container test-container-subpath-dynamicpv-4fnt: <nil>
STEP: delete the pod
Jun 13 16:29:08.059: INFO: Waiting for pod pod-subpath-test-dynamicpv-4fnt to disappear
Jun 13 16:29:08.090: INFO: Pod pod-subpath-test-dynamicpv-4fnt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4fnt
Jun 13 16:29:08.090: INFO: Deleting pod "pod-subpath-test-dynamicpv-4fnt" in namespace "provisioning-4743"
... skipping 97 lines ...
Jun 13 16:28:55.179: INFO: PersistentVolumeClaim pvc-w9wnl found but phase is Pending instead of Bound.
Jun 13 16:28:57.211: INFO: PersistentVolumeClaim pvc-w9wnl found and phase=Bound (10.204008046s)
Jun 13 16:28:57.211: INFO: Waiting up to 3m0s for PersistentVolume aws-jccg9 to have phase Bound
Jun 13 16:28:57.243: INFO: PersistentVolume aws-jccg9 found and phase=Bound (31.388972ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-hdjx
STEP: Creating a pod to test exec-volume-test
Jun 13 16:28:57.348: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-hdjx" in namespace "volume-1325" to be "Succeeded or Failed"
Jun 13 16:28:57.381: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.835846ms
Jun 13 16:28:59.413: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064642253s
Jun 13 16:29:01.444: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096061498s
Jun 13 16:29:03.476: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127837174s
Jun 13 16:29:05.508: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159793641s
Jun 13 16:29:07.540: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.191867863s
STEP: Saw pod success
Jun 13 16:29:07.540: INFO: Pod "exec-volume-test-preprovisionedpv-hdjx" satisfied condition "Succeeded or Failed"
Jun 13 16:29:07.571: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-hdjx container exec-container-preprovisionedpv-hdjx: <nil>
STEP: delete the pod
Jun 13 16:29:07.647: INFO: Waiting for pod exec-volume-test-preprovisionedpv-hdjx to disappear
Jun 13 16:29:07.679: INFO: Pod exec-volume-test-preprovisionedpv-hdjx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-hdjx
Jun 13 16:29:07.679: INFO: Deleting pod "exec-volume-test-preprovisionedpv-hdjx" in namespace "volume-1325"
STEP: Deleting pv and pvc
Jun 13 16:29:07.711: INFO: Deleting PersistentVolumeClaim "pvc-w9wnl"
Jun 13 16:29:07.744: INFO: Deleting PersistentVolume "aws-jccg9"
Jun 13 16:29:07.902: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: abe06533-3899-4928-b10a-794ed975daf6
Jun 13 16:29:13.188: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 91e8434f-4c72-4a80-a3a4-ddcbc0c59287
Jun 13 16:29:18.464: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: ade2d40d-3eb0-4b39-a0b5-36dc0fb8e64e
Jun 13 16:29:23.782: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 114afe5d-7cba-4780-be76-49e060c84257
Jun 13 16:29:29.011: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 708fac64-46e0-46ce-b2b0-79f1223639e1
Jun 13 16:29:34.299: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: f9ba4edc-a9cc-45e1-b690-2cecd3bfa818
Jun 13 16:29:39.524: INFO: Couldn't delete PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06837b8c5a3b38b9b is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 27e1d926-722f-4757-b8db-97e239c60323
Jun 13 16:29:44.787: INFO: Successfully deleted PD "aws://ca-central-1a/vol-06837b8c5a3b38b9b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:29:44.787: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1325" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:28:45.526: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 13 16:28:45.688: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:28:45.688: INFO: Creating resource for dynamic PV
Jun 13 16:28:45.688: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1600hzqlg
STEP: creating a claim
Jun 13 16:28:45.724: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-q4v5
STEP: Checking for subpath error in container status
Jun 13 16:29:09.907: INFO: Deleting pod "pod-subpath-test-dynamicpv-q4v5" in namespace "provisioning-1600"
Jun 13 16:29:09.940: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-q4v5" to be fully deleted
STEP: Deleting pod
Jun 13 16:29:20.003: INFO: Deleting pod "pod-subpath-test-dynamicpv-q4v5" in namespace "provisioning-1600"
STEP: Deleting pvc
Jun 13 16:29:20.098: INFO: Deleting PersistentVolumeClaim "awsjb8xm"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 13 16:28:07.068: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5307-e2e-scnd2hr
STEP: creating a claim
Jun 13 16:28:07.100: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b7n4
STEP: Creating a pod to test subpath
Jun 13 16:28:07.204: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b7n4" in namespace "provisioning-5307" to be "Succeeded or Failed"
Jun 13 16:28:07.238: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 34.475397ms
Jun 13 16:28:09.275: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070952212s
Jun 13 16:28:11.309: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104936134s
Jun 13 16:28:13.340: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136644106s
Jun 13 16:28:15.372: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168159085s
Jun 13 16:28:17.405: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.200795317s
... skipping 10 lines ...
Jun 13 16:28:39.764: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.56047642s
Jun 13 16:28:41.796: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 34.592299139s
Jun 13 16:28:43.828: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 36.623763445s
Jun 13 16:28:45.863: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 38.659185351s
Jun 13 16:28:47.896: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.692041671s
STEP: Saw pod success
Jun 13 16:28:47.896: INFO: Pod "pod-subpath-test-dynamicpv-b7n4" satisfied condition "Succeeded or Failed"
Jun 13 16:28:47.927: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-b7n4 container test-container-subpath-dynamicpv-b7n4: <nil>
STEP: delete the pod
Jun 13 16:28:48.000: INFO: Waiting for pod pod-subpath-test-dynamicpv-b7n4 to disappear
Jun 13 16:28:48.033: INFO: Pod pod-subpath-test-dynamicpv-b7n4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b7n4
Jun 13 16:28:48.033: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7n4" in namespace "provisioning-5307"
STEP: Creating pod pod-subpath-test-dynamicpv-b7n4
STEP: Creating a pod to test subpath
Jun 13 16:28:48.098: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b7n4" in namespace "provisioning-5307" to be "Succeeded or Failed"
Jun 13 16:28:48.129: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 31.512599ms
Jun 13 16:28:50.161: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063045745s
Jun 13 16:28:52.193: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094967924s
Jun 13 16:28:54.225: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127686948s
Jun 13 16:28:56.258: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160067191s
Jun 13 16:28:58.289: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191770381s
Jun 13 16:29:00.321: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223723561s
Jun 13 16:29:02.354: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.255999044s
Jun 13 16:29:04.386: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288776962s
Jun 13 16:29:06.419: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320950648s
Jun 13 16:29:08.450: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.352664292s
Jun 13 16:29:10.482: INFO: Pod "pod-subpath-test-dynamicpv-b7n4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.384671708s
STEP: Saw pod success
Jun 13 16:29:10.482: INFO: Pod "pod-subpath-test-dynamicpv-b7n4" satisfied condition "Succeeded or Failed"
Jun 13 16:29:10.514: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-b7n4 container test-container-subpath-dynamicpv-b7n4: <nil>
STEP: delete the pod
Jun 13 16:29:10.588: INFO: Waiting for pod pod-subpath-test-dynamicpv-b7n4 to disappear
Jun 13 16:29:10.619: INFO: Pod pod-subpath-test-dynamicpv-b7n4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b7n4
Jun 13 16:29:10.620: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7n4" in namespace "provisioning-5307"
... skipping 464 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 11 lines ...
Jun 13 16:29:03.111: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7525-e2e-scbx54s
STEP: creating a claim
Jun 13 16:29:03.143: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4rth
STEP: Creating a pod to test subpath
Jun 13 16:29:03.241: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4rth" in namespace "provisioning-7525" to be "Succeeded or Failed"
Jun 13 16:29:03.271: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 30.270717ms
Jun 13 16:29:05.303: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061362612s
Jun 13 16:29:07.340: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098590195s
Jun 13 16:29:09.371: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129958951s
Jun 13 16:29:11.403: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161657245s
Jun 13 16:29:13.435: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193609419s
... skipping 2 lines ...
Jun 13 16:29:19.530: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288323701s
Jun 13 16:29:21.562: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320319321s
Jun 13 16:29:23.592: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 20.35123288s
Jun 13 16:29:25.624: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Pending", Reason="", readiness=false. Elapsed: 22.38258234s
Jun 13 16:29:27.655: INFO: Pod "pod-subpath-test-dynamicpv-4rth": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.41383728s
STEP: Saw pod success
Jun 13 16:29:27.655: INFO: Pod "pod-subpath-test-dynamicpv-4rth" satisfied condition "Succeeded or Failed"
Jun 13 16:29:27.686: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-4rth container test-container-subpath-dynamicpv-4rth: <nil>
STEP: delete the pod
Jun 13 16:29:27.757: INFO: Waiting for pod pod-subpath-test-dynamicpv-4rth to disappear
Jun 13 16:29:27.787: INFO: Pod pod-subpath-test-dynamicpv-4rth no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4rth
Jun 13 16:29:27.787: INFO: Deleting pod "pod-subpath-test-dynamicpv-4rth" in namespace "provisioning-7525"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 102 lines ...
Jun 13 16:29:35.154: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5116sxnd7
STEP: creating a claim
Jun 13 16:29:35.187: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 13 16:29:35.252: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 16:29:35.315: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:37.384: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:39.379: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:41.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:43.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:45.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:47.387: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:49.381: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:51.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:53.385: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:55.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:57.384: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:29:59.382: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:30:01.383: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:30:03.391: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:30:05.387: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5116sxnd7",
  	... // 2 identical fields
  }

Jun 13 16:30:05.450: INFO: Error updating pvc awsf5j8v: PersistentVolumeClaim "awsf5j8v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 63 lines ...

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

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

    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 192 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:29:28.572: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 13 16:29:28.752: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:29:28.752: INFO: Creating resource for dynamic PV
Jun 13 16:29:28.752: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9902vthrw
STEP: creating a claim
Jun 13 16:29:28.784: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p9d4
STEP: Checking for subpath error in container status
Jun 13 16:29:56.949: INFO: Deleting pod "pod-subpath-test-dynamicpv-p9d4" in namespace "provisioning-9902"
Jun 13 16:29:56.983: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p9d4" to be fully deleted
STEP: Deleting pod
Jun 13 16:30:03.057: INFO: Deleting pod "pod-subpath-test-dynamicpv-p9d4" in namespace "provisioning-9902"
STEP: Deleting pvc
Jun 13 16:30:03.154: INFO: Deleting PersistentVolumeClaim "awsjd9zn"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes:vsphere [Feature:vsphere]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:30:23.580: INFO: >>> kubeConfig: /root/.kube/config
... skipping 11 lines ...
Jun 13 16:30:23.815: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 153 lines ...
Jun 13 16:29:46.354: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-52374rrdd
STEP: creating a claim
Jun 13 16:29:46.385: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t9z7
STEP: Creating a pod to test multi_subpath
Jun 13 16:29:46.485: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t9z7" in namespace "provisioning-5237" to be "Succeeded or Failed"
Jun 13 16:29:46.517: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.118062ms
Jun 13 16:29:48.549: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063607973s
Jun 13 16:29:50.587: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102374444s
Jun 13 16:29:52.623: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138327993s
Jun 13 16:29:54.655: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170360781s
Jun 13 16:29:56.688: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202631481s
... skipping 2 lines ...
Jun 13 16:30:02.795: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.310293125s
Jun 13 16:30:04.827: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 18.342290653s
Jun 13 16:30:06.860: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 20.374998496s
Jun 13 16:30:08.894: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Pending", Reason="", readiness=false. Elapsed: 22.409283485s
Jun 13 16:30:10.943: INFO: Pod "pod-subpath-test-dynamicpv-t9z7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.458395004s
STEP: Saw pod success
Jun 13 16:30:10.944: INFO: Pod "pod-subpath-test-dynamicpv-t9z7" satisfied condition "Succeeded or Failed"
Jun 13 16:30:10.978: INFO: Trying to get logs from node ip-172-20-40-132.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-t9z7 container test-container-subpath-dynamicpv-t9z7: <nil>
STEP: delete the pod
Jun 13 16:30:11.065: INFO: Waiting for pod pod-subpath-test-dynamicpv-t9z7 to disappear
Jun 13 16:30:11.111: INFO: Pod pod-subpath-test-dynamicpv-t9z7 no longer exists
STEP: Deleting pod
Jun 13 16:30:11.111: INFO: Deleting pod "pod-subpath-test-dynamicpv-t9z7" in namespace "provisioning-5237"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 147 lines ...
Jun 13 16:30:17.025: INFO: Waiting for pod aws-client to disappear
Jun 13 16:30:17.055: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 16:30:17.055: INFO: Deleting PersistentVolumeClaim "pvc-fxbzq"
Jun 13 16:30:17.091: INFO: Deleting PersistentVolume "aws-b4tkh"
Jun 13 16:30:17.380: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ee0f40ebedade3b7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee0f40ebedade3b7 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 5fb6530c-5140-4fd3-8ef4-fe1a206c72a5
Jun 13 16:30:22.651: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ee0f40ebedade3b7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee0f40ebedade3b7 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 5a28f0bf-b428-4429-86b9-ee1214ad42ee
Jun 13 16:30:27.951: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ee0f40ebedade3b7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee0f40ebedade3b7 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 516b1a32-b5af-4931-811e-6519ce165bf3
Jun 13 16:30:33.227: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0ee0f40ebedade3b7".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:30:33.227: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1355" for this suite.
... skipping 68 lines ...
Jun 13 16:27:28.695: INFO: Creating resource for dynamic PV
Jun 13 16:27:28.695: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2548-e2e-sc94pw8
STEP: creating a claim
Jun 13 16:27:28.729: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 16:27:28.826: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-skwnq" in namespace "snapshotting-2548" to be "Succeeded or Failed"
Jun 13 16:27:28.857: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 30.991604ms
Jun 13 16:27:30.891: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06477185s
Jun 13 16:27:32.922: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096455332s
Jun 13 16:27:34.954: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127619094s
Jun 13 16:27:36.987: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161338964s
Jun 13 16:27:39.019: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192796666s
Jun 13 16:27:41.050: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.224103037s
Jun 13 16:27:43.082: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.255771403s
Jun 13 16:27:45.114: INFO: Pod "pvc-snapshottable-tester-skwnq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.287668284s
STEP: Saw pod success
Jun 13 16:27:45.114: INFO: Pod "pvc-snapshottable-tester-skwnq" satisfied condition "Succeeded or Failed"
Jun 13 16:27:45.210: INFO: Pod pvc-snapshottable-tester-skwnq has the following logs: 
Jun 13 16:27:45.210: INFO: Deleting pod "pvc-snapshottable-tester-skwnq" in namespace "snapshotting-2548"
Jun 13 16:27:45.246: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-skwnq" to be fully deleted
Jun 13 16:27:45.276: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comszbxg] to have phase Bound
Jun 13 16:27:45.307: INFO: PersistentVolumeClaim ebs.csi.aws.comszbxg found and phase=Bound (30.747874ms)
STEP: [init] checking the claim
... skipping 26 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XAbxy8blG/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 13 16:28:18.199: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-l52m7" in namespace "snapshotting-2548" to be "Succeeded or Failed"
Jun 13 16:28:18.230: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.74137ms
Jun 13 16:28:20.261: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06187734s
Jun 13 16:28:22.294: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094373136s
Jun 13 16:28:24.329: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130126878s
Jun 13 16:28:26.361: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161562221s
Jun 13 16:28:28.392: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192737633s
... skipping 7 lines ...
Jun 13 16:28:44.655: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 26.455524317s
Jun 13 16:28:46.688: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.488591995s
Jun 13 16:28:48.720: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.521096019s
Jun 13 16:28:50.752: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.552484744s
Jun 13 16:28:52.785: INFO: Pod "pvc-snapshottable-data-tester-l52m7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.585434171s
STEP: Saw pod success
Jun 13 16:28:52.785: INFO: Pod "pvc-snapshottable-data-tester-l52m7" satisfied condition "Succeeded or Failed"
Jun 13 16:28:52.850: INFO: Pod pvc-snapshottable-data-tester-l52m7 has the following logs: 
Jun 13 16:28:52.850: INFO: Deleting pod "pvc-snapshottable-data-tester-l52m7" in namespace "snapshotting-2548"
Jun 13 16:28:52.889: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-l52m7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 16:29:17.052: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2548 exec restored-pvc-tester-hqflc --namespace=snapshotting-2548 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun 13 16:29:42.520: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:43.552: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:44.587: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:45.619: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:46.652: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:47.686: INFO: volumesnapshotcontents snapcontent-863eacf8-bc09-43b3-a378-7ad0380f64fa has been found and is not deleted
Jun 13 16:29:48.687: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 13 16:29:48.723: INFO: Pod restored-pvc-tester-hqflc has the following logs: 
Jun 13 16:29:48.723: INFO: Deleting pod "restored-pvc-tester-hqflc" in namespace "snapshotting-2548"
Jun 13 16:29:48.758: INFO: Wait up to 5m0s for pod "restored-pvc-tester-hqflc" to be fully deleted
Jun 13 16:30:26.826: INFO: deleting claim "snapshotting-2548"/"pvc-j8x88"
... skipping 210 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 176 lines ...
Jun 13 16:28:41.785: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2526rgqdb      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-2526    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-2526rgqdb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2526    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-2526rgqdb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2526    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-2526rgqdb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2526rgqdb    60f8e8d4-5401-41f0-9b3a-15a66b5f8f69 5017 0 2021-06-13 16:28:41 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-13 16:28:41 +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-5vxvx pvc- provisioning-2526  4cd8eac7-83b9-4831-9168-aa4773be6255 5021 0 2021-06-13 16:28:41 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-13 16:28:41 +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-2526rgqdb,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-cdadf751-0d85-4030-8182-518dd7a986b0 in namespace provisioning-2526
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 13 16:28:56.132: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-njkt8" in namespace "provisioning-2526" to be "Succeeded or Failed"
Jun 13 16:28:56.163: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.191942ms
Jun 13 16:28:58.194: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062355442s
Jun 13 16:29:00.226: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093819653s
Jun 13 16:29:02.258: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125601337s
Jun 13 16:29:04.289: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156409798s
Jun 13 16:29:06.321: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188945355s
... skipping 23 lines ...
Jun 13 16:29:55.087: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 58.955102786s
Jun 13 16:29:57.121: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.988940922s
Jun 13 16:29:59.155: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.023132976s
Jun 13 16:30:01.191: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.059134837s
Jun 13 16:30:03.227: INFO: Pod "pvc-volume-tester-writer-njkt8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.095127203s
STEP: Saw pod success
Jun 13 16:30:03.227: INFO: Pod "pvc-volume-tester-writer-njkt8" satisfied condition "Succeeded or Failed"
Jun 13 16:30:03.295: INFO: Pod pvc-volume-tester-writer-njkt8 has the following logs: 
Jun 13 16:30:03.347: INFO: Deleting pod "pvc-volume-tester-writer-njkt8" in namespace "provisioning-2526"
Jun 13 16:30:03.387: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-njkt8" 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-40-132.ca-central-1.compute.internal"
Jun 13 16:30:03.521: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-6qr44" in namespace "provisioning-2526" to be "Succeeded or Failed"
Jun 13 16:30:03.555: INFO: Pod "pvc-volume-tester-reader-6qr44": Phase="Pending", Reason="", readiness=false. Elapsed: 34.352211ms
Jun 13 16:30:05.589: INFO: Pod "pvc-volume-tester-reader-6qr44": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068535232s
Jun 13 16:30:07.623: INFO: Pod "pvc-volume-tester-reader-6qr44": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.102432853s
STEP: Saw pod success
Jun 13 16:30:07.623: INFO: Pod "pvc-volume-tester-reader-6qr44" satisfied condition "Succeeded or Failed"
Jun 13 16:30:07.710: INFO: Pod pvc-volume-tester-reader-6qr44 has the following logs: hello world

Jun 13 16:30:07.710: INFO: Deleting pod "pvc-volume-tester-reader-6qr44" in namespace "provisioning-2526"
Jun 13 16:30:07.751: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-6qr44" to be fully deleted
Jun 13 16:30:07.787: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5vxvx] to have phase Bound
Jun 13 16:30:07.819: INFO: PersistentVolumeClaim pvc-5vxvx found and phase=Bound (32.321329ms)
... skipping 486 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 284 lines ...
Jun 13 16:30:06.295: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1773-e2e-sctv94k
STEP: creating a claim
Jun 13 16:30:06.328: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d5tk
STEP: Creating a pod to test subpath
Jun 13 16:30:06.431: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d5tk" in namespace "provisioning-1773" to be "Succeeded or Failed"
Jun 13 16:30:06.463: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 32.097189ms
Jun 13 16:30:08.499: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067284207s
Jun 13 16:30:10.535: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104108192s
Jun 13 16:30:12.576: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.144951989s
Jun 13 16:30:14.611: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.180083533s
Jun 13 16:30:16.643: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.211449993s
Jun 13 16:30:18.678: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.247125452s
Jun 13 16:30:20.715: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.284088508s
Jun 13 16:30:22.751: INFO: Pod "pod-subpath-test-dynamicpv-d5tk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.319326934s
STEP: Saw pod success
Jun 13 16:30:22.751: INFO: Pod "pod-subpath-test-dynamicpv-d5tk" satisfied condition "Succeeded or Failed"
Jun 13 16:30:22.783: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-d5tk container test-container-volume-dynamicpv-d5tk: <nil>
STEP: delete the pod
Jun 13 16:30:22.855: INFO: Waiting for pod pod-subpath-test-dynamicpv-d5tk to disappear
Jun 13 16:30:22.887: INFO: Pod pod-subpath-test-dynamicpv-d5tk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d5tk
Jun 13 16:30:22.887: INFO: Deleting pod "pod-subpath-test-dynamicpv-d5tk" in namespace "provisioning-1773"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 322 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:30:37.169: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:30:37.339: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 16:30:37.799: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-08efab642b44212c0".
Jun 13 16:30:37.799: INFO: Creating resource for pre-provisioned PV
Jun 13 16:30:37.799: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun 13 16:30:37.967: INFO: PersistentVolumeClaim pvc-xms2x found but phase is Pending instead of Bound.
Jun 13 16:30:40.011: INFO: PersistentVolumeClaim pvc-xms2x found but phase is Pending instead of Bound.
Jun 13 16:30:42.043: INFO: PersistentVolumeClaim pvc-xms2x found and phase=Bound (4.107827698s)
Jun 13 16:30:42.043: INFO: Waiting up to 3m0s for PersistentVolume aws-sb4rm to have phase Bound
Jun 13 16:30:42.077: INFO: PersistentVolume aws-sb4rm found and phase=Bound (33.938824ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:30:44.286: INFO: Deleting pod "pod-26560904-d50d-4de3-b96b-82e21b7596fb" in namespace "volumemode-2905"
Jun 13 16:30:44.320: INFO: Wait up to 5m0s for pod "pod-26560904-d50d-4de3-b96b-82e21b7596fb" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 16:30:54.386: INFO: Deleting PersistentVolumeClaim "pvc-xms2x"
Jun 13 16:30:54.422: INFO: Deleting PersistentVolume "aws-sb4rm"
Jun 13 16:30:54.590: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08efab642b44212c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08efab642b44212c0 is currently attached to i-0fb12f0c3872fc21c
	status code: 400, request id: 79a4cad4-c58b-49d4-b65e-17fafbf15c8b
Jun 13 16:31:00.139: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08efab642b44212c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08efab642b44212c0 is currently attached to i-0fb12f0c3872fc21c
	status code: 400, request id: 2ba9a31e-092b-4465-980b-3eff3105a03a
Jun 13 16:31:05.399: INFO: Successfully deleted PD "aws://ca-central-1a/vol-08efab642b44212c0".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:31:05.399: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2905" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 16:31:05.470: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
... skipping 84 lines ...

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

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

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

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

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

    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 265 lines ...
Jun 13 16:30:23.987: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 16:30:24.451: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0e2289d925a2578dc".
Jun 13 16:30:24.451: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-rxzc
STEP: Creating a pod to test exec-volume-test
Jun 13 16:30:24.487: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-rxzc" in namespace "volume-7858" to be "Succeeded or Failed"
Jun 13 16:30:24.523: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 36.683343ms
Jun 13 16:30:26.558: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07184618s
Jun 13 16:30:28.591: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104729884s
Jun 13 16:30:30.627: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140776332s
Jun 13 16:30:32.660: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173754631s
Jun 13 16:30:34.696: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209407864s
Jun 13 16:30:36.730: INFO: Pod "exec-volume-test-inlinevolume-rxzc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.243474257s
STEP: Saw pod success
Jun 13 16:30:36.730: INFO: Pod "exec-volume-test-inlinevolume-rxzc" satisfied condition "Succeeded or Failed"
Jun 13 16:30:36.763: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-rxzc container exec-container-inlinevolume-rxzc: <nil>
STEP: delete the pod
Jun 13 16:30:36.840: INFO: Waiting for pod exec-volume-test-inlinevolume-rxzc to disappear
Jun 13 16:30:36.875: INFO: Pod exec-volume-test-inlinevolume-rxzc no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-rxzc
Jun 13 16:30:36.875: INFO: Deleting pod "exec-volume-test-inlinevolume-rxzc" in namespace "volume-7858"
Jun 13 16:30:37.048: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: eefe7c51-1b73-41d9-8027-a71737ad0451
Jun 13 16:30:42.312: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 86679dbc-28b7-4630-a826-16b7c835576a
Jun 13 16:30:47.600: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 5ded37ab-43ac-49ee-8c73-5bf1277842ae
Jun 13 16:30:52.843: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 0d879a71-8768-4498-bcad-3cffb06a8186
Jun 13 16:30:58.135: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: a050e991-4e89-4827-88a0-9435bde2162f
Jun 13 16:31:03.413: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e2289d925a2578dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e2289d925a2578dc is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 0a5b4247-a581-4bb6-8c55-c0398aa06878
Jun 13 16:31:08.702: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0e2289d925a2578dc".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:31:08.702: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7858" for this suite.
... skipping 83 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:30:55.595: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:30:55.759: INFO: Creating resource for dynamic PV
Jun 13 16:30:55.759: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6898-e2e-scqdhfg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:31:01.991: INFO: Deleting pod "pod-7af57f66-d064-4c6e-866d-50fa3c04ba82" in namespace "volumemode-6898"
Jun 13 16:31:02.023: INFO: Wait up to 5m0s for pod "pod-7af57f66-d064-4c6e-866d-50fa3c04ba82" to be fully deleted
STEP: Deleting pvc
Jun 13 16:31:10.171: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comthp2r"
Jun 13 16:31:10.275: INFO: Waiting up to 5m0s for PersistentVolume pvc-4ede7d50-a1fb-4c41-bd53-076a1d83d08d to get deleted
Jun 13 16:31:10.315: INFO: PersistentVolume pvc-4ede7d50-a1fb-4c41-bd53-076a1d83d08d found and phase=Bound (39.731492ms)
... skipping 7 lines ...

• [SLOW TEST:19.849 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 392 lines ...
Jun 13 16:30:58.888: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-17658zb8p
STEP: creating a claim
Jun 13 16:30:58.923: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bg5b
STEP: Creating a pod to test subpath
Jun 13 16:30:59.033: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bg5b" in namespace "provisioning-1765" to be "Succeeded or Failed"
Jun 13 16:30:59.064: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 30.67975ms
Jun 13 16:31:01.099: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066037059s
Jun 13 16:31:03.131: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097934285s
Jun 13 16:31:05.167: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.134042473s
Jun 13 16:31:07.203: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169981633s
Jun 13 16:31:09.243: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209866039s
... skipping 2 lines ...
Jun 13 16:31:15.341: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 16.307862481s
Jun 13 16:31:17.375: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 18.341967553s
Jun 13 16:31:19.422: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 20.388293441s
Jun 13 16:31:21.453: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Pending", Reason="", readiness=false. Elapsed: 22.419369617s
Jun 13 16:31:23.484: INFO: Pod "pod-subpath-test-dynamicpv-bg5b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.450327426s
STEP: Saw pod success
Jun 13 16:31:23.484: INFO: Pod "pod-subpath-test-dynamicpv-bg5b" satisfied condition "Succeeded or Failed"
Jun 13 16:31:23.514: INFO: Trying to get logs from node ip-172-20-40-132.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-bg5b container test-container-volume-dynamicpv-bg5b: <nil>
STEP: delete the pod
Jun 13 16:31:23.583: INFO: Waiting for pod pod-subpath-test-dynamicpv-bg5b to disappear
Jun 13 16:31:23.615: INFO: Pod pod-subpath-test-dynamicpv-bg5b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bg5b
Jun 13 16:31:23.615: INFO: Deleting pod "pod-subpath-test-dynamicpv-bg5b" in namespace "provisioning-1765"
... skipping 165 lines ...
Jun 13 16:31:03.791: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8302-e2e-sc49629
STEP: creating a claim
Jun 13 16:31:03.827: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-f6rb
STEP: Creating a pod to test exec-volume-test
Jun 13 16:31:03.931: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-f6rb" in namespace "volume-8302" to be "Succeeded or Failed"
Jun 13 16:31:03.963: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 31.959022ms
Jun 13 16:31:06.000: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06893275s
Jun 13 16:31:08.039: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107985648s
Jun 13 16:31:10.075: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.143710146s
Jun 13 16:31:12.110: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.178764522s
Jun 13 16:31:14.142: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.210196299s
Jun 13 16:31:16.174: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.243107654s
Jun 13 16:31:18.207: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.27595082s
Jun 13 16:31:20.243: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.311944886s
Jun 13 16:31:22.281: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.349791444s
Jun 13 16:31:24.323: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.391989104s
Jun 13 16:31:26.356: INFO: Pod "exec-volume-test-dynamicpv-f6rb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.424840462s
STEP: Saw pod success
Jun 13 16:31:26.356: INFO: Pod "exec-volume-test-dynamicpv-f6rb" satisfied condition "Succeeded or Failed"
Jun 13 16:31:26.388: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-f6rb container exec-container-dynamicpv-f6rb: <nil>
STEP: delete the pod
Jun 13 16:31:26.461: INFO: Waiting for pod exec-volume-test-dynamicpv-f6rb to disappear
Jun 13 16:31:26.492: INFO: Pod exec-volume-test-dynamicpv-f6rb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-f6rb
Jun 13 16:31:26.493: INFO: Deleting pod "exec-volume-test-dynamicpv-f6rb" in namespace "volume-8302"
... skipping 77 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 62 lines ...
STEP: Deleting pod hostexec-ip-172-20-52-62.ca-central-1.compute.internal-fwqwf in namespace volumemode-6383
Jun 13 16:31:16.905: INFO: Deleting pod "pod-2a7af2fe-4ac2-40c8-9e3f-cf0dfc1147be" in namespace "volumemode-6383"
Jun 13 16:31:16.939: INFO: Wait up to 5m0s for pod "pod-2a7af2fe-4ac2-40c8-9e3f-cf0dfc1147be" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 16:31:27.007: INFO: Deleting PersistentVolumeClaim "pvc-44wm6"
Jun 13 16:31:27.040: INFO: Deleting PersistentVolume "aws-9gfcj"
Jun 13 16:31:27.226: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b2674aae3019383d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2674aae3019383d is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 20fe6cfc-c5c0-4ad3-880e-d9248d090e06
Jun 13 16:31:32.507: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b2674aae3019383d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2674aae3019383d is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: b791fd08-d8e9-4fd0-a777-e499ba1a6d54
Jun 13 16:31:37.803: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b2674aae3019383d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2674aae3019383d is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 15bc07d9-6905-4127-9edd-d9ae6e959cde
Jun 13 16:31:43.120: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b2674aae3019383d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2674aae3019383d is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: b0884e6e-9dfa-45e3-ac31-a79cf3115bf8
Jun 13 16:31:48.375: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0b2674aae3019383d".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:31:48.375: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6383" for this suite.
... skipping 114 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:30:40.089: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 13 16:30:40.267: INFO: Creating resource for dynamic PV
Jun 13 16:30:40.267: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5898-e2e-scn648m
STEP: creating a claim
Jun 13 16:30:40.302: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bxw6
STEP: Checking for subpath error in container status
Jun 13 16:31:04.468: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxw6" in namespace "provisioning-5898"
Jun 13 16:31:04.503: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bxw6" to be fully deleted
STEP: Deleting pod
Jun 13 16:31:16.570: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxw6" in namespace "provisioning-5898"
STEP: Deleting pvc
Jun 13 16:31:16.671: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comf6ljz"
... skipping 15 lines ...

• [SLOW TEST:71.986 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 16:31:52.079: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
... skipping 52 lines ...
Jun 13 16:31:15.378: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-24027tpr9
STEP: creating a claim
Jun 13 16:31:15.413: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-4wzp
STEP: Creating a pod to test exec-volume-test
Jun 13 16:31:15.514: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4wzp" in namespace "volume-2402" to be "Succeeded or Failed"
Jun 13 16:31:15.545: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.779036ms
Jun 13 16:31:17.579: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065282426s
Jun 13 16:31:19.611: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097170804s
Jun 13 16:31:21.642: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128252158s
Jun 13 16:31:23.674: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160074206s
Jun 13 16:31:25.707: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193282618s
Jun 13 16:31:27.743: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.229299824s
Jun 13 16:31:29.774: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.260386442s
Jun 13 16:31:31.806: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.292376963s
Jun 13 16:31:33.842: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.328325015s
Jun 13 16:31:35.874: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.359932345s
Jun 13 16:31:37.906: INFO: Pod "exec-volume-test-dynamicpv-4wzp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.392232351s
STEP: Saw pod success
Jun 13 16:31:37.906: INFO: Pod "exec-volume-test-dynamicpv-4wzp" satisfied condition "Succeeded or Failed"
Jun 13 16:31:37.939: INFO: Trying to get logs from node ip-172-20-40-132.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-4wzp container exec-container-dynamicpv-4wzp: <nil>
STEP: delete the pod
Jun 13 16:31:38.013: INFO: Waiting for pod exec-volume-test-dynamicpv-4wzp to disappear
Jun 13 16:31:38.047: INFO: Pod exec-volume-test-dynamicpv-4wzp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4wzp
Jun 13 16:31:38.047: INFO: Deleting pod "exec-volume-test-dynamicpv-4wzp" in namespace "volume-2402"
... skipping 36 lines ...
Jun 13 16:31:17.709: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 16:31:18.247: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-059e4d258585dac13".
Jun 13 16:31:18.247: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-sbs9
STEP: Creating a pod to test exec-volume-test
Jun 13 16:31:18.282: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-sbs9" in namespace "volume-2404" to be "Succeeded or Failed"
Jun 13 16:31:18.314: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 32.476941ms
Jun 13 16:31:20.347: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065732374s
Jun 13 16:31:22.388: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106843729s
Jun 13 16:31:24.420: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138518048s
Jun 13 16:31:26.451: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169861103s
Jun 13 16:31:28.483: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201016994s
... skipping 7 lines ...
Jun 13 16:31:44.747: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 26.465614738s
Jun 13 16:31:46.778: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 28.496667109s
Jun 13 16:31:48.811: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 30.52908641s
Jun 13 16:31:50.847: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 32.565659964s
Jun 13 16:31:52.880: INFO: Pod "exec-volume-test-inlinevolume-sbs9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.598293628s
STEP: Saw pod success
Jun 13 16:31:52.880: INFO: Pod "exec-volume-test-inlinevolume-sbs9" satisfied condition "Succeeded or Failed"
Jun 13 16:31:52.911: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-sbs9 container exec-container-inlinevolume-sbs9: <nil>
STEP: delete the pod
Jun 13 16:31:53.015: INFO: Waiting for pod exec-volume-test-inlinevolume-sbs9 to disappear
Jun 13 16:31:53.059: INFO: Pod exec-volume-test-inlinevolume-sbs9 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-sbs9
Jun 13 16:31:53.059: INFO: Deleting pod "exec-volume-test-inlinevolume-sbs9" in namespace "volume-2404"
Jun 13 16:31:53.279: INFO: Couldn't delete PD "aws://ca-central-1a/vol-059e4d258585dac13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-059e4d258585dac13 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 6056424b-2f7a-4565-8a07-3db05ade0ecc
Jun 13 16:31:58.555: INFO: Couldn't delete PD "aws://ca-central-1a/vol-059e4d258585dac13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-059e4d258585dac13 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 493ea06b-b319-4c25-9935-9d962bacea01
Jun 13 16:32:03.834: INFO: Successfully deleted PD "aws://ca-central-1a/vol-059e4d258585dac13".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:32:03.834: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2404" for this suite.
... skipping 429 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 112 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:31:39.259: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 16:31:39.432: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:31:39.432: INFO: Creating resource for dynamic PV
Jun 13 16:31:39.432: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8110qpd9x
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 16:31:43.659: INFO: Deleting pod "pod-061c3784-a01c-4b29-9707-f4fcc614eab4" in namespace "volumemode-8110"
Jun 13 16:31:43.695: INFO: Wait up to 5m0s for pod "pod-061c3784-a01c-4b29-9707-f4fcc614eab4" to be fully deleted
STEP: Deleting pvc
Jun 13 16:31:49.823: INFO: Deleting PersistentVolumeClaim "aws92gcs"
Jun 13 16:31:49.855: INFO: Waiting up to 5m0s for PersistentVolume pvc-8e392742-d3d8-479b-8e91-fc5925715086 to get deleted
Jun 13 16:31:49.887: INFO: PersistentVolume pvc-8e392742-d3d8-479b-8e91-fc5925715086 found and phase=Released (32.021941ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 75 lines ...
Jun 13 16:31:08.970: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2877-e2e-sccdcfk
STEP: creating a claim
Jun 13 16:31:09.003: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-c94v
STEP: Creating a pod to test exec-volume-test
Jun 13 16:31:09.109: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-c94v" in namespace "volume-2877" to be "Succeeded or Failed"
Jun 13 16:31:09.141: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 31.618885ms
Jun 13 16:31:11.175: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065840856s
Jun 13 16:31:13.219: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109902194s
Jun 13 16:31:15.253: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.143745065s
Jun 13 16:31:17.287: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.177837051s
Jun 13 16:31:19.323: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213869687s
Jun 13 16:31:21.355: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.246068486s
Jun 13 16:31:23.388: INFO: Pod "exec-volume-test-dynamicpv-c94v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.278126975s
STEP: Saw pod success
Jun 13 16:31:23.388: INFO: Pod "exec-volume-test-dynamicpv-c94v" satisfied condition "Succeeded or Failed"
Jun 13 16:31:23.419: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-c94v container exec-container-dynamicpv-c94v: <nil>
STEP: delete the pod
Jun 13 16:31:23.490: INFO: Waiting for pod exec-volume-test-dynamicpv-c94v to disappear
Jun 13 16:31:23.522: INFO: Pod exec-volume-test-dynamicpv-c94v no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-c94v
Jun 13 16:31:23.522: INFO: Deleting pod "exec-volume-test-dynamicpv-c94v" in namespace "volume-2877"
... skipping 134 lines ...
Jun 13 16:29:44.015: INFO: Creating resource for dynamic PV
Jun 13 16:29:44.015: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9682-e2e-sc7wszr
STEP: creating a claim
Jun 13 16:29:44.051: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 16:29:44.153: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gmjgt" in namespace "snapshotting-9682" to be "Succeeded or Failed"
Jun 13 16:29:44.186: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 32.753411ms
Jun 13 16:29:46.218: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064457323s
Jun 13 16:29:48.251: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098009609s
Jun 13 16:29:50.291: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138019886s
Jun 13 16:29:52.327: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.174017055s
Jun 13 16:29:54.360: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206955825s
Jun 13 16:29:56.392: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.238284696s
Jun 13 16:29:58.425: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.272001335s
Jun 13 16:30:00.459: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.306108465s
Jun 13 16:30:02.491: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.338020851s
Jun 13 16:30:04.527: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.374037235s
Jun 13 16:30:06.563: INFO: Pod "pvc-snapshottable-tester-gmjgt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.410035493s
STEP: Saw pod success
Jun 13 16:30:06.563: INFO: Pod "pvc-snapshottable-tester-gmjgt" satisfied condition "Succeeded or Failed"
Jun 13 16:30:06.627: INFO: Pod pvc-snapshottable-tester-gmjgt has the following logs: 
Jun 13 16:30:06.627: INFO: Deleting pod "pvc-snapshottable-tester-gmjgt" in namespace "snapshotting-9682"
Jun 13 16:30:06.667: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gmjgt" to be fully deleted
Jun 13 16:30:06.703: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com8fqsm] to have phase Bound
Jun 13 16:30:06.739: INFO: PersistentVolumeClaim ebs.csi.aws.com8fqsm found and phase=Bound (36.072691ms)
STEP: [init] checking the claim
... skipping 34 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XAbxy8blG/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 13 16:30:56.011: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-jww55" in namespace "snapshotting-9682" to be "Succeeded or Failed"
Jun 13 16:30:56.042: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 30.807534ms
Jun 13 16:30:58.075: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063276311s
Jun 13 16:31:00.106: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09486164s
Jun 13 16:31:02.143: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13183216s
Jun 13 16:31:04.179: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 8.167858575s
Jun 13 16:31:06.211: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 10.199749798s
Jun 13 16:31:08.255: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 12.243312144s
Jun 13 16:31:10.295: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 14.28391631s
Jun 13 16:31:12.329: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Pending", Reason="", readiness=false. Elapsed: 16.31725125s
Jun 13 16:31:14.360: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Running", Reason="", readiness=true. Elapsed: 18.3483451s
Jun 13 16:31:16.391: INFO: Pod "pvc-snapshottable-data-tester-jww55": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.379251697s
STEP: Saw pod success
Jun 13 16:31:16.391: INFO: Pod "pvc-snapshottable-data-tester-jww55" satisfied condition "Succeeded or Failed"
Jun 13 16:31:16.457: INFO: Pod pvc-snapshottable-data-tester-jww55 has the following logs: 
Jun 13 16:31:16.457: INFO: Deleting pod "pvc-snapshottable-data-tester-jww55" in namespace "snapshotting-9682"
Jun 13 16:31:16.494: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-jww55" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 16:31:54.659: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9682 exec restored-pvc-tester-gx4kg --namespace=snapshotting-9682 -- cat /mnt/test/data'
... skipping 43 lines ...
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:12 +0000 UTC - event for pvc-snapshottable-data-tester-jww55: {kubelet ip-172-20-52-220.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:16 +0000 UTC - event for pvc-w9sn5: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:16 +0000 UTC - event for pvc-w9sn5: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-bvms4_33787e3f-d569-454c-b1a3-575b54b4b0bd } Provisioning: External provisioner is provisioning volume for claim "snapshotting-9682/pvc-w9sn5"
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:16 +0000 UTC - event for pvc-w9sn5: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:20 +0000 UTC - event for pvc-w9sn5: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-bvms4_33787e3f-d569-454c-b1a3-575b54b4b0bd } ProvisioningSucceeded: Successfully provisioned volume pvc-1474fec7-f054-4a55-b6a3-4f13ea0668a3
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:20 +0000 UTC - event for restored-pvc-tester-gx4kg: {default-scheduler } Scheduled: Successfully assigned snapshotting-9682/restored-pvc-tester-gx4kg to ip-172-20-52-62.ca-central-1.compute.internal
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:41 +0000 UTC - event for restored-pvc-tester-gx4kg: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-1474fec7-f054-4a55-b6a3-4f13ea0668a3" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:47 +0000 UTC - event for restored-pvc-tester-gx4kg: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-1474fec7-f054-4a55-b6a3-4f13ea0668a3" 
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:53 +0000 UTC - event for restored-pvc-tester-gx4kg: {kubelet ip-172-20-52-62.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:53 +0000 UTC - event for restored-pvc-tester-gx4kg: {kubelet ip-172-20-52-62.ca-central-1.compute.internal} Created: Created container volume-tester
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:53 +0000 UTC - event for restored-pvc-tester-gx4kg: {kubelet ip-172-20-52-62.ca-central-1.compute.internal} Started: Started container volume-tester
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:31:56 +0000 UTC - event for restored-pvc-tester-gx4kg: {kubelet ip-172-20-52-62.ca-central-1.compute.internal} Killing: Stopping container volume-tester
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:32:31 +0000 UTC - event for snapshot-hp8vw: {snapshot-controller } SnapshotContentObjectDeleteError: Failed to delete snapshot content API object
Jun 13 16:32:37.018: INFO: At 2021-06-13 16:32:32 +0000 UTC - event for snapshot-hp8vw: {snapshot-controller } GetSnapshotClassFailed: Failed to get snapshot class with error volumesnapshotclass.snapshot.storage.k8s.io "snapshotting-9682-vscc89mc" not found
Jun 13 16:32:37.048: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 13 16:32:37.048: INFO: 
Jun 13 16:32:37.080: INFO: 
Logging node info for node ip-172-20-40-132.ca-central-1.compute.internal
Jun 13 16:32:37.116: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-40-132.ca-central-1.compute.internal    59dc7c0f-2440-4989-a187-3fe3fe9f446b 11276 0 2021-06-13 16:22:35 +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:ca-central-1 failure-domain.beta.kubernetes.io/zone:ca-central-1a kops.k8s.io/instancegroup:nodes-ca-central-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-40-132.ca-central-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ca-central-1a topology.kubernetes.io/region:ca-central-1 topology.kubernetes.io/zone:ca-central-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0fb12f0c3872fc21c"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.40.132/19 projectcalico.org/IPv4IPIPTunnelAddr:100.124.138.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-13 16:22:35 +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-13 16:22:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-13 16:27:36 +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":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-13 16:32:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///ca-central-1a/i-0fb12f0c3872fc21c,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.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: {{4064751616 0} {<nil>} 3969484Ki 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: {{3959894016 0} {<nil>} 3867084Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-13 16:22:52 +0000 UTC,LastTransitionTime:2021-06-13 16:22:52 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:27 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:27 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:27 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-13 16:32:27 +0000 UTC,LastTransitionTime:2021-06-13 16:22:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.40.132,},NodeAddress{Type:ExternalIP,Address:3.96.149.254,},NodeAddress{Type:Hostname,Address:ip-172-20-40-132.ca-central-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-40-132.ca-central-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-3-96-149-254.ca-central-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec25ca114e7dcb49e8e0642ba4d98260,SystemUUID:ec25ca11-4e7d-cb49-e8e0-642ba4d98260,BootID:c6de70fa-5335-4107-94cd-396429eec174,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:[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:[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:[kubernetes.io/csi/ebs.csi.aws.com^vol-001ff0ab7e9db1058 kubernetes.io/csi/ebs.csi.aws.com^vol-0547f9e4cdbe8c9ef kubernetes.io/csi/ebs.csi.aws.com^vol-08a8d623d53930617],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-08a8d623d53930617,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0547f9e4cdbe8c9ef,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-001ff0ab7e9db1058,DevicePath:,},},Config:nil,},}
Jun 13 16:32:37.117: INFO: 
... skipping 206 lines ...
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.XAbxy8blG/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.XAbxy8blG/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-9682 exec restored-pvc-tester-gx4kg --namespace=snapshotting-9682 -- 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-9682 exec restored-pvc-tester-gx4kg --namespace=snapshotting-9682 -- 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 99 lines ...
Jun 13 16:31:52.473: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2521sxvrl
STEP: creating a claim
Jun 13 16:31:52.505: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-v729
STEP: Creating a pod to test subpath
Jun 13 16:31:52.608: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-v729" in namespace "provisioning-2521" to be "Succeeded or Failed"
Jun 13 16:31:52.639: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 31.332641ms
Jun 13 16:31:54.675: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067669105s
Jun 13 16:31:56.708: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100266817s
Jun 13 16:31:58.743: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135093856s
Jun 13 16:32:00.779: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 8.1717557s
Jun 13 16:32:02.819: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 10.211761725s
... skipping 2 lines ...
Jun 13 16:32:08.931: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 16.32380325s
Jun 13 16:32:10.967: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 18.359676393s
Jun 13 16:32:13.011: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 20.40335896s
Jun 13 16:32:15.044: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Pending", Reason="", readiness=false. Elapsed: 22.436360862s
Jun 13 16:32:17.076: INFO: Pod "pod-subpath-test-dynamicpv-v729": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.468475608s
STEP: Saw pod success
Jun 13 16:32:17.076: INFO: Pod "pod-subpath-test-dynamicpv-v729" satisfied condition "Succeeded or Failed"
Jun 13 16:32:17.108: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-v729 container test-container-subpath-dynamicpv-v729: <nil>
STEP: delete the pod
Jun 13 16:32:17.192: INFO: Waiting for pod pod-subpath-test-dynamicpv-v729 to disappear
Jun 13 16:32:17.224: INFO: Pod pod-subpath-test-dynamicpv-v729 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-v729
Jun 13 16:32:17.224: INFO: Deleting pod "pod-subpath-test-dynamicpv-v729" in namespace "provisioning-2521"
... skipping 89 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:32:15.167: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 13 16:32:15.323: INFO: Creating resource for dynamic PV
Jun 13 16:32:15.323: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9689-e2e-scpbhzn
STEP: creating a claim
Jun 13 16:32:15.355: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h5nb
STEP: Checking for subpath error in container status
Jun 13 16:32:27.519: INFO: Deleting pod "pod-subpath-test-dynamicpv-h5nb" in namespace "provisioning-9689"
Jun 13 16:32:27.551: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-h5nb" to be fully deleted
STEP: Deleting pod
Jun 13 16:32:39.615: INFO: Deleting pod "pod-subpath-test-dynamicpv-h5nb" in namespace "provisioning-9689"
STEP: Deleting pvc
Jun 13 16:32:39.711: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comb8k5r"
... skipping 10 lines ...

• [SLOW TEST:34.781 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 195 lines ...
Jun 13 16:32:37.125: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:37.156: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 16:32:37.156: INFO: Deleting PersistentVolumeClaim "pvc-m69d2"
Jun 13 16:32:37.190: INFO: Deleting PersistentVolume "aws-qfswd"
Jun 13 16:32:37.471: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0464b2f17216649ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0464b2f17216649ba is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 69d67a35-95b7-44dd-9d36-71e3bd7740ab
Jun 13 16:32:42.714: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0464b2f17216649ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0464b2f17216649ba is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 120fdc41-d73b-42ce-99ca-3b8f7da6fc45
Jun 13 16:32:47.966: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0464b2f17216649ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0464b2f17216649ba is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: d485164c-2efc-4cd9-b760-afd6dfe9d38c
Jun 13 16:32:53.216: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0464b2f17216649ba".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:32:53.216: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3336" for this suite.
... skipping 89 lines ...
Jun 13 16:32:37.950: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:37.980: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 16:32:37.980: INFO: Deleting PersistentVolumeClaim "pvc-8mg92"
Jun 13 16:32:38.012: INFO: Deleting PersistentVolume "aws-dvdw6"
Jun 13 16:32:38.263: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02a856e6b2e0a21a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02a856e6b2e0a21a0 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 7bf1e850-ed0c-4e68-8218-1a37f19bc0e6
Jun 13 16:32:43.509: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02a856e6b2e0a21a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02a856e6b2e0a21a0 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 82308852-7a36-489c-b913-0ce9d45f423a
Jun 13 16:32:48.772: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02a856e6b2e0a21a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02a856e6b2e0a21a0 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 7f75f691-4b25-44a6-af64-8049549f573b
Jun 13 16:32:54.003: INFO: Successfully deleted PD "aws://ca-central-1a/vol-02a856e6b2e0a21a0".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:32:54.003: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8838" for this suite.
... skipping 232 lines ...
Jun 13 16:30:38.757: INFO: Creating resource for dynamic PV
Jun 13 16:30:38.757: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8227-e2e-sc9b24v
STEP: creating a claim
Jun 13 16:30:38.788: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 16:30:38.887: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-jtl4v" in namespace "snapshotting-8227" to be "Succeeded or Failed"
Jun 13 16:30:38.918: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 30.90104ms
Jun 13 16:30:40.951: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063875728s
Jun 13 16:30:42.983: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095245705s
Jun 13 16:30:45.014: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126147746s
Jun 13 16:30:47.047: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159930814s
Jun 13 16:30:49.083: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.195992538s
Jun 13 16:30:51.119: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.232091867s
Jun 13 16:30:53.151: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 14.263870837s
Jun 13 16:30:55.187: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 16.29986777s
Jun 13 16:30:57.220: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 18.332859932s
Jun 13 16:30:59.255: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Pending", Reason="", readiness=false. Elapsed: 20.367879124s
Jun 13 16:31:01.289: INFO: Pod "pvc-snapshottable-tester-jtl4v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.401900594s
STEP: Saw pod success
Jun 13 16:31:01.289: INFO: Pod "pvc-snapshottable-tester-jtl4v" satisfied condition "Succeeded or Failed"
Jun 13 16:31:01.357: INFO: Pod pvc-snapshottable-tester-jtl4v has the following logs: 
Jun 13 16:31:01.357: INFO: Deleting pod "pvc-snapshottable-tester-jtl4v" in namespace "snapshotting-8227"
Jun 13 16:31:01.395: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-jtl4v" to be fully deleted
Jun 13 16:31:01.427: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comq95sm] to have phase Bound
Jun 13 16:31:01.459: INFO: PersistentVolumeClaim ebs.csi.aws.comq95sm found and phase=Bound (32.009594ms)
STEP: [init] checking the claim
... skipping 47 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XAbxy8blG/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 13 16:31:40.833: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-dqtrp" in namespace "snapshotting-8227" to be "Succeeded or Failed"
Jun 13 16:31:40.863: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.302453ms
Jun 13 16:31:42.898: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065028739s
Jun 13 16:31:44.935: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102281597s
Jun 13 16:31:46.970: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136828299s
Jun 13 16:31:49.002: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168878818s
Jun 13 16:31:51.035: INFO: Pod "pvc-snapshottable-data-tester-dqtrp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.202313906s
STEP: Saw pod success
Jun 13 16:31:51.035: INFO: Pod "pvc-snapshottable-data-tester-dqtrp" satisfied condition "Succeeded or Failed"
Jun 13 16:31:51.099: INFO: Pod pvc-snapshottable-data-tester-dqtrp has the following logs: 
Jun 13 16:31:51.099: INFO: Deleting pod "pvc-snapshottable-data-tester-dqtrp" in namespace "snapshotting-8227"
Jun 13 16:31:51.143: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-dqtrp" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 16:32:05.327: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8227 exec restored-pvc-tester-p6fh2 --namespace=snapshotting-8227 -- cat /mnt/test/data'
... skipping 48 lines ...
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:31:55 +0000 UTC - event for restored-pvc-tester-p6fh2: {default-scheduler } Scheduled: Successfully assigned snapshotting-8227/restored-pvc-tester-p6fh2 to ip-172-20-40-132.ca-central-1.compute.internal
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:00 +0000 UTC - event for restored-pvc-tester-p6fh2: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-9599100f-92b3-48d3-beb7-f7a4bef10653" 
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:03 +0000 UTC - event for restored-pvc-tester-p6fh2: {kubelet ip-172-20-40-132.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:03 +0000 UTC - event for restored-pvc-tester-p6fh2: {kubelet ip-172-20-40-132.ca-central-1.compute.internal} Created: Created container volume-tester
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:03 +0000 UTC - event for restored-pvc-tester-p6fh2: {kubelet ip-172-20-40-132.ca-central-1.compute.internal} Started: Started container volume-tester
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:07 +0000 UTC - event for restored-pvc-tester-p6fh2: {kubelet ip-172-20-40-132.ca-central-1.compute.internal} Killing: Stopping container volume-tester
Jun 13 16:32:55.626: INFO: At 2021-06-13 16:32:50 +0000 UTC - event for pre-provisioned-snapshot-62d4f2fe-96fe-4931-9c74-362244f845ee: {snapshot-controller } SnapshotContentObjectDeleteError: Failed to delete snapshot content API object
Jun 13 16:32:55.656: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 13 16:32:55.656: INFO: 
Jun 13 16:32:55.688: INFO: 
Logging node info for node ip-172-20-40-132.ca-central-1.compute.internal
Jun 13 16:32:55.721: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-40-132.ca-central-1.compute.internal    59dc7c0f-2440-4989-a187-3fe3fe9f446b 11861 0 2021-06-13 16:22:35 +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:ca-central-1 failure-domain.beta.kubernetes.io/zone:ca-central-1a kops.k8s.io/instancegroup:nodes-ca-central-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-40-132.ca-central-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ca-central-1a topology.kubernetes.io/region:ca-central-1 topology.kubernetes.io/zone:ca-central-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0fb12f0c3872fc21c"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.40.132/19 projectcalico.org/IPv4IPIPTunnelAddr:100.124.138.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-13 16:22:35 +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-13 16:22:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-13 16:27:36 +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":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-13 16:32:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///ca-central-1a/i-0fb12f0c3872fc21c,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.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: {{4064751616 0} {<nil>} 3969484Ki 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: {{3959894016 0} {<nil>} 3867084Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-13 16:22:52 +0000 UTC,LastTransitionTime:2021-06-13 16:22:52 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:47 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:47 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-13 16:32:47 +0000 UTC,LastTransitionTime:2021-06-13 16:22:35 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-13 16:32:47 +0000 UTC,LastTransitionTime:2021-06-13 16:22:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.40.132,},NodeAddress{Type:ExternalIP,Address:3.96.149.254,},NodeAddress{Type:Hostname,Address:ip-172-20-40-132.ca-central-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-40-132.ca-central-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-3-96-149-254.ca-central-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec25ca114e7dcb49e8e0642ba4d98260,SystemUUID:ec25ca11-4e7d-cb49-e8e0-642ba4d98260,BootID:c6de70fa-5335-4107-94cd-396429eec174,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:[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:[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:[kubernetes.io/csi/ebs.csi.aws.com^vol-001ff0ab7e9db1058 kubernetes.io/csi/ebs.csi.aws.com^vol-0673a6d8a072d3b87],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0673a6d8a072d3b87,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-001ff0ab7e9db1058,DevicePath:,},},Config:nil,},}
Jun 13 16:32:55.722: INFO: 
... skipping 186 lines ...
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.XAbxy8blG/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.XAbxy8blG/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-8227 exec restored-pvc-tester-p6fh2 --namespace=snapshotting-8227 -- 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-8227 exec restored-pvc-tester-p6fh2 --namespace=snapshotting-8227 -- 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-stress
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 518 lines ...
Jun 13 16:32:45.930: INFO: Pod aws-client still exists
Jun 13 16:32:47.898: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:47.930: INFO: Pod aws-client still exists
Jun 13 16:32:49.899: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:49.930: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 16:32:50.216: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01457baa010ded438", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01457baa010ded438 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: b9cf4614-4b95-44dc-b791-102832a320be
Jun 13 16:32:55.494: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01457baa010ded438", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01457baa010ded438 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: 1e185039-92cf-4e81-8f73-14fb17969790
Jun 13 16:33:00.814: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01457baa010ded438", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01457baa010ded438 is currently attached to i-08dd86541f63eec2f
	status code: 400, request id: b5f48326-ed47-4213-a5ae-df46c5572e59
Jun 13 16:33:06.086: INFO: Successfully deleted PD "aws://ca-central-1a/vol-01457baa010ded438".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:33:06.086: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8933" for this suite.
... skipping 209 lines ...
Jun 13 16:32:53.708: INFO: Pod aws-client still exists
Jun 13 16:32:55.675: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:55.712: INFO: Pod aws-client still exists
Jun 13 16:32:57.675: INFO: Waiting for pod aws-client to disappear
Jun 13 16:32:57.709: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 16:32:57.924: INFO: Couldn't delete PD "aws://ca-central-1a/vol-04a80bad74229bed2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a80bad74229bed2 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: d0514dfc-e4c6-41f9-9b83-56e09f50dbc5
Jun 13 16:33:03.216: INFO: Couldn't delete PD "aws://ca-central-1a/vol-04a80bad74229bed2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a80bad74229bed2 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 2b43ebc7-480f-42da-801f-772b2dd952be
Jun 13 16:33:08.462: INFO: Successfully deleted PD "aws://ca-central-1a/vol-04a80bad74229bed2".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:33:08.463: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4019" for this suite.
... skipping 26 lines ...
Jun 13 16:32:40.418: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9432wwm8t
STEP: creating a claim
Jun 13 16:32:40.450: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pxqc
STEP: Creating a pod to test exec-volume-test
Jun 13 16:32:40.547: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pxqc" in namespace "volume-9432" to be "Succeeded or Failed"
Jun 13 16:32:40.578: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 30.560513ms
Jun 13 16:32:42.609: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061927468s
Jun 13 16:32:44.643: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095968943s
Jun 13 16:32:46.677: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12996652s
Jun 13 16:32:48.708: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161136977s
Jun 13 16:32:50.742: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194809684s
Jun 13 16:32:52.774: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226287682s
Jun 13 16:32:54.805: INFO: Pod "exec-volume-test-dynamicpv-pxqc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.257806385s
STEP: Saw pod success
Jun 13 16:32:54.805: INFO: Pod "exec-volume-test-dynamicpv-pxqc" satisfied condition "Succeeded or Failed"
Jun 13 16:32:54.836: INFO: Trying to get logs from node ip-172-20-40-132.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-pxqc container exec-container-dynamicpv-pxqc: <nil>
STEP: delete the pod
Jun 13 16:32:54.907: INFO: Waiting for pod exec-volume-test-dynamicpv-pxqc to disappear
Jun 13 16:32:54.937: INFO: Pod exec-volume-test-dynamicpv-pxqc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pxqc
Jun 13 16:32:54.937: INFO: Deleting pod "exec-volume-test-dynamicpv-pxqc" in namespace "volume-9432"
... skipping 112 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:32:28.065: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 13 16:32:28.229: INFO: Creating resource for dynamic PV
Jun 13 16:32:28.229: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2924-e2e-scsn25g
STEP: creating a claim
Jun 13 16:32:28.262: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5hv9
STEP: Checking for subpath error in container status
Jun 13 16:32:44.422: INFO: Deleting pod "pod-subpath-test-dynamicpv-5hv9" in namespace "provisioning-2924"
Jun 13 16:32:44.457: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5hv9" to be fully deleted
STEP: Deleting pod
Jun 13 16:32:56.520: INFO: Deleting pod "pod-subpath-test-dynamicpv-5hv9" in namespace "provisioning-2924"
STEP: Deleting pvc
Jun 13 16:32:56.642: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2p2cz"
... skipping 12 lines ...

• [SLOW TEST:48.868 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 16:33:16.936: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 97 lines ...
STEP: Deleting pod hostexec-ip-172-20-52-62.ca-central-1.compute.internal-8sfmp in namespace volumemode-8386
Jun 13 16:33:01.085: INFO: Deleting pod "pod-a2f6262b-04a8-467c-8a98-461db40b2a50" in namespace "volumemode-8386"
Jun 13 16:33:01.117: INFO: Wait up to 5m0s for pod "pod-a2f6262b-04a8-467c-8a98-461db40b2a50" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 16:33:07.183: INFO: Deleting PersistentVolumeClaim "pvc-ttbzd"
Jun 13 16:33:07.215: INFO: Deleting PersistentVolume "aws-rfh4p"
Jun 13 16:33:07.402: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b01605a1a7a507a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b01605a1a7a507a0 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: c6385b93-10e0-4ec1-8d58-821a14e93faf
Jun 13 16:33:12.681: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b01605a1a7a507a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b01605a1a7a507a0 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 496388ef-a623-4364-8d14-4e557bc49ccd
Jun 13 16:33:17.944: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0b01605a1a7a507a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b01605a1a7a507a0 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 55a3298c-0a7a-4262-aa9a-5c0f89df1885
Jun 13 16:33:23.202: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0b01605a1a7a507a0".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:33:23.203: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8386" for this suite.
... skipping 390 lines ...
Jun 13 16:33:23.781: INFO: PersistentVolumeClaim pvc-zhqbf found but phase is Pending instead of Bound.
Jun 13 16:33:25.812: INFO: PersistentVolumeClaim pvc-zhqbf found and phase=Bound (8.156985889s)
Jun 13 16:33:25.812: INFO: Waiting up to 3m0s for PersistentVolume aws-6gprw to have phase Bound
Jun 13 16:33:25.843: INFO: PersistentVolume aws-6gprw found and phase=Bound (30.984532ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-c9r6
STEP: Creating a pod to test exec-volume-test
Jun 13 16:33:25.936: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-c9r6" in namespace "volume-5137" to be "Succeeded or Failed"
Jun 13 16:33:25.967: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.702299ms
Jun 13 16:33:27.999: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062750218s
Jun 13 16:33:30.031: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0944069s
Jun 13 16:33:32.062: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125865993s
Jun 13 16:33:34.093: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.156925699s
STEP: Saw pod success
Jun 13 16:33:34.093: INFO: Pod "exec-volume-test-preprovisionedpv-c9r6" satisfied condition "Succeeded or Failed"
Jun 13 16:33:34.126: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-c9r6 container exec-container-preprovisionedpv-c9r6: <nil>
STEP: delete the pod
Jun 13 16:33:34.202: INFO: Waiting for pod exec-volume-test-preprovisionedpv-c9r6 to disappear
Jun 13 16:33:34.235: INFO: Pod exec-volume-test-preprovisionedpv-c9r6 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-c9r6
Jun 13 16:33:34.235: INFO: Deleting pod "exec-volume-test-preprovisionedpv-c9r6" in namespace "volume-5137"
STEP: Deleting pv and pvc
Jun 13 16:33:34.267: INFO: Deleting PersistentVolumeClaim "pvc-zhqbf"
Jun 13 16:33:34.300: INFO: Deleting PersistentVolume "aws-6gprw"
Jun 13 16:33:34.500: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0bfcb9fc672f9a402", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bfcb9fc672f9a402 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 362a34a4-5aa4-403c-9d80-0b7f7dd41b93
Jun 13 16:33:39.726: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0bfcb9fc672f9a402", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bfcb9fc672f9a402 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: b3e5e778-9452-4980-8cab-373292441fd4
Jun 13 16:33:44.993: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0bfcb9fc672f9a402".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:33:44.993: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5137" for this suite.
... skipping 22 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 201 lines ...
Jun 13 16:33:23.426: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-26182vf96
STEP: creating a claim
Jun 13 16:33:23.458: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xhd4
STEP: Creating a pod to test subpath
Jun 13 16:33:23.556: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xhd4" in namespace "provisioning-2618" to be "Succeeded or Failed"
Jun 13 16:33:23.588: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Pending", Reason="", readiness=false. Elapsed: 31.360682ms
Jun 13 16:33:25.620: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063558214s
Jun 13 16:33:27.652: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095603056s
Jun 13 16:33:29.685: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128887464s
Jun 13 16:33:31.717: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160565426s
Jun 13 16:33:33.750: INFO: Pod "pod-subpath-test-dynamicpv-xhd4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.19367483s
STEP: Saw pod success
Jun 13 16:33:33.750: INFO: Pod "pod-subpath-test-dynamicpv-xhd4" satisfied condition "Succeeded or Failed"
Jun 13 16:33:33.781: INFO: Trying to get logs from node ip-172-20-52-220.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-xhd4 container test-container-subpath-dynamicpv-xhd4: <nil>
STEP: delete the pod
Jun 13 16:33:33.860: INFO: Waiting for pod pod-subpath-test-dynamicpv-xhd4 to disappear
Jun 13 16:33:33.891: INFO: Pod pod-subpath-test-dynamicpv-xhd4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xhd4
Jun 13 16:33:33.891: INFO: Deleting pod "pod-subpath-test-dynamicpv-xhd4" in namespace "provisioning-2618"
... skipping 118 lines ...
Jun 13 16:32:56.434: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7861-e2e-scj4s6z
STEP: creating a claim
Jun 13 16:32:56.467: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-fjzf
STEP: Creating a pod to test exec-volume-test
Jun 13 16:32:56.571: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-fjzf" in namespace "volume-7861" to be "Succeeded or Failed"
Jun 13 16:32:56.620: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 48.709677ms
Jun 13 16:32:58.655: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084007522s
Jun 13 16:33:00.692: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120811602s
Jun 13 16:33:02.724: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.152777463s
Jun 13 16:33:04.756: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.18467161s
Jun 13 16:33:06.788: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216842366s
Jun 13 16:33:08.821: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.249550664s
Jun 13 16:33:10.860: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.289093469s
Jun 13 16:33:12.896: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.325225102s
Jun 13 16:33:14.929: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.357714971s
Jun 13 16:33:16.960: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.389108125s
Jun 13 16:33:18.993: INFO: Pod "exec-volume-test-dynamicpv-fjzf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.421731924s
STEP: Saw pod success
Jun 13 16:33:18.993: INFO: Pod "exec-volume-test-dynamicpv-fjzf" satisfied condition "Succeeded or Failed"
Jun 13 16:33:19.024: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-fjzf container exec-container-dynamicpv-fjzf: <nil>
STEP: delete the pod
Jun 13 16:33:19.094: INFO: Waiting for pod exec-volume-test-dynamicpv-fjzf to disappear
Jun 13 16:33:19.125: INFO: Pod exec-volume-test-dynamicpv-fjzf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-fjzf
Jun 13 16:33:19.125: INFO: Deleting pod "exec-volume-test-dynamicpv-fjzf" in namespace "volume-7861"
... skipping 313 lines ...
Jun 13 16:34:02.246: INFO: Pod aws-client still exists
Jun 13 16:34:04.215: INFO: Waiting for pod aws-client to disappear
Jun 13 16:34:04.246: INFO: Pod aws-client still exists
Jun 13 16:34:06.215: INFO: Waiting for pod aws-client to disappear
Jun 13 16:34:06.246: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 16:34:06.386: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0d26f6f1289f04b75", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d26f6f1289f04b75 is currently attached to i-0bcfebe1720b1d3ed
	status code: 400, request id: 512f5b99-b3a7-4c7f-8732-02aa39529f08
Jun 13 16:34:11.674: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0d26f6f1289f04b75".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:34:11.674: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3820" for this suite.
... skipping 96 lines ...
Jun 13 16:32:58.768: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3068vv476
STEP: creating a claim
Jun 13 16:32:58.800: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lql4
STEP: Creating a pod to test subpath
Jun 13 16:32:58.895: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lql4" in namespace "provisioning-3068" to be "Succeeded or Failed"
Jun 13 16:32:58.928: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.565605ms
Jun 13 16:33:00.959: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063913244s
Jun 13 16:33:02.992: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096095877s
Jun 13 16:33:05.040: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.144084106s
Jun 13 16:33:07.072: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.176140082s
Jun 13 16:33:09.103: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.207083702s
... skipping 10 lines ...
Jun 13 16:33:31.461: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.565230997s
Jun 13 16:33:33.493: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 34.597154512s
Jun 13 16:33:35.530: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 36.634195727s
Jun 13 16:33:37.563: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Pending", Reason="", readiness=false. Elapsed: 38.667705309s
Jun 13 16:33:39.595: INFO: Pod "pod-subpath-test-dynamicpv-lql4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.699425826s
STEP: Saw pod success
Jun 13 16:33:39.595: INFO: Pod "pod-subpath-test-dynamicpv-lql4" satisfied condition "Succeeded or Failed"
Jun 13 16:33:39.626: INFO: Trying to get logs from node ip-172-20-54-27.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-lql4 container test-container-volume-dynamicpv-lql4: <nil>
STEP: delete the pod
Jun 13 16:33:39.699: INFO: Waiting for pod pod-subpath-test-dynamicpv-lql4 to disappear
Jun 13 16:33:39.729: INFO: Pod pod-subpath-test-dynamicpv-lql4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lql4
Jun 13 16:33:39.729: INFO: Deleting pod "pod-subpath-test-dynamicpv-lql4" in namespace "provisioning-3068"
... skipping 73 lines ...
Jun 13 16:33:50.274: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6818-e2e-scfltbt
STEP: creating a claim
Jun 13 16:33:50.310: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 13 16:33:50.373: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 16:33:50.438: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:33:52.501: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:33:54.503: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:33:56.503: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:33:58.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:00.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:02.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:04.501: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:06.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:08.503: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:10.501: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:12.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:14.503: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:16.503: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:18.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:20.502: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6818-e2e-scfltbt",
  	... // 2 identical fields
  }

Jun 13 16:34:20.564: INFO: Error updating pvc ebs.csi.aws.com5wxkm: PersistentVolumeClaim "ebs.csi.aws.com5wxkm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 120 lines ...
Jun 13 16:32:29.947: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8700sqlxl
STEP: creating a claim
Jun 13 16:32:29.979: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gqsx
STEP: Creating a pod to test subpath
Jun 13 16:32:30.082: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gqsx" in namespace "provisioning-8700" to be "Succeeded or Failed"
Jun 13 16:32:30.115: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.093779ms
Jun 13 16:32:32.148: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065510836s
Jun 13 16:32:34.179: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097195995s
Jun 13 16:32:36.217: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13452671s
Jun 13 16:32:38.252: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169606289s
Jun 13 16:32:40.284: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202129649s
Jun 13 16:32:42.316: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.234012118s
Jun 13 16:32:44.350: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.267936243s
STEP: Saw pod success
Jun 13 16:32:44.350: INFO: Pod "pod-subpath-test-dynamicpv-gqsx" satisfied condition "Succeeded or Failed"
Jun 13 16:32:44.381: INFO: Trying to get logs from node ip-172-20-52-220.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-gqsx container test-container-subpath-dynamicpv-gqsx: <nil>
STEP: delete the pod
Jun 13 16:32:44.453: INFO: Waiting for pod pod-subpath-test-dynamicpv-gqsx to disappear
Jun 13 16:32:44.484: INFO: Pod pod-subpath-test-dynamicpv-gqsx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gqsx
Jun 13 16:32:44.484: INFO: Deleting pod "pod-subpath-test-dynamicpv-gqsx" in namespace "provisioning-8700"
STEP: Creating pod pod-subpath-test-dynamicpv-gqsx
STEP: Creating a pod to test subpath
Jun 13 16:32:44.551: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gqsx" in namespace "provisioning-8700" to be "Succeeded or Failed"
Jun 13 16:32:44.586: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.672212ms
Jun 13 16:32:46.618: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066758262s
Jun 13 16:32:48.651: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099597609s
Jun 13 16:32:50.683: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13139761s
Jun 13 16:32:52.715: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.163231429s
Jun 13 16:32:54.752: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.200246227s
... skipping 23 lines ...
Jun 13 16:33:43.543: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 58.9910982s
Jun 13 16:33:45.574: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.022847192s
Jun 13 16:33:47.606: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.054699003s
Jun 13 16:33:49.638: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.086931454s
Jun 13 16:33:51.671: INFO: Pod "pod-subpath-test-dynamicpv-gqsx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.119276046s
STEP: Saw pod success
Jun 13 16:33:51.671: INFO: Pod "pod-subpath-test-dynamicpv-gqsx" satisfied condition "Succeeded or Failed"
Jun 13 16:33:51.702: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-gqsx container test-container-subpath-dynamicpv-gqsx: <nil>
STEP: delete the pod
Jun 13 16:33:51.775: INFO: Waiting for pod pod-subpath-test-dynamicpv-gqsx to disappear
Jun 13 16:33:51.806: INFO: Pod pod-subpath-test-dynamicpv-gqsx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gqsx
Jun 13 16:33:51.806: INFO: Deleting pod "pod-subpath-test-dynamicpv-gqsx" in namespace "provisioning-8700"
... skipping 134 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 142 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:34:31.537: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 13 16:34:31.759: INFO: found topology map[topology.kubernetes.io/zone:ca-central-1a]
Jun 13 16:34:31.759: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 16:34:31.759: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XAbxy8blG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 348 lines ...
Jun 13 16:34:31.429: INFO: Waiting for pod aws-client to disappear
Jun 13 16:34:31.460: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 16:34:31.461: INFO: Deleting PersistentVolumeClaim "pvc-c2gmt"
Jun 13 16:34:31.494: INFO: Deleting PersistentVolume "aws-mpnf8"
Jun 13 16:34:31.766: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08642af07f16ead21", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08642af07f16ead21 is currently attached to i-0af67519cec7ed402
	status code: 400, request id: dfc87a07-8624-4d83-8522-4d5d556012f0
Jun 13 16:34:37.032: INFO: Successfully deleted PD "aws://ca-central-1a/vol-08642af07f16ead21".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:34:37.032: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8268" for this suite.
... skipping 688 lines ...
Jun 13 16:34:21.546: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 16:34:21.949: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-08913b751997bcd6f".
Jun 13 16:34:21.949: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-dl86
STEP: Creating a pod to test exec-volume-test
Jun 13 16:34:21.983: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-dl86" in namespace "volume-7092" to be "Succeeded or Failed"
Jun 13 16:34:22.014: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 30.765848ms
Jun 13 16:34:24.045: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061602382s
Jun 13 16:34:26.087: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103763565s
Jun 13 16:34:28.120: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136268025s
Jun 13 16:34:30.153: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170227167s
Jun 13 16:34:32.186: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20246301s
Jun 13 16:34:34.217: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 12.233958748s
Jun 13 16:34:36.250: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 14.266365671s
Jun 13 16:34:38.282: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 16.298434188s
Jun 13 16:34:40.316: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 18.332330402s
Jun 13 16:34:42.348: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Pending", Reason="", readiness=false. Elapsed: 20.364274033s
Jun 13 16:34:44.390: INFO: Pod "exec-volume-test-inlinevolume-dl86": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.40694564s
STEP: Saw pod success
Jun 13 16:34:44.390: INFO: Pod "exec-volume-test-inlinevolume-dl86" satisfied condition "Succeeded or Failed"
Jun 13 16:34:44.431: INFO: Trying to get logs from node ip-172-20-52-220.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-dl86 container exec-container-inlinevolume-dl86: <nil>
STEP: delete the pod
Jun 13 16:34:44.518: INFO: Waiting for pod exec-volume-test-inlinevolume-dl86 to disappear
Jun 13 16:34:44.549: INFO: Pod exec-volume-test-inlinevolume-dl86 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-dl86
Jun 13 16:34:44.549: INFO: Deleting pod "exec-volume-test-inlinevolume-dl86" in namespace "volume-7092"
Jun 13 16:34:44.727: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08913b751997bcd6f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08913b751997bcd6f is currently attached to i-0af67519cec7ed402
	status code: 400, request id: bb9771dd-3633-4e4f-9f53-f8717ea623b2
Jun 13 16:34:50.001: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08913b751997bcd6f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08913b751997bcd6f is currently attached to i-0af67519cec7ed402
	status code: 400, request id: 7190039f-086f-4e8f-88bb-da134f2eb366
Jun 13 16:34:55.281: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08913b751997bcd6f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08913b751997bcd6f is currently attached to i-0af67519cec7ed402
	status code: 400, request id: 13f83f98-6f51-4ef7-be84-2d6e00a05412
Jun 13 16:35:00.541: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08913b751997bcd6f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08913b751997bcd6f is currently attached to i-0af67519cec7ed402
	status code: 400, request id: 62852900-2129-4377-8b2c-7635124cf2b8
Jun 13 16:35:05.794: INFO: Successfully deleted PD "aws://ca-central-1a/vol-08913b751997bcd6f".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 16:35:05.794: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7092" for this suite.
... skipping 61 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 16:34:32.809: 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 13 16:34:32.966: INFO: Creating resource for dynamic PV
Jun 13 16:34:32.966: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7192-e2e-scgp4zs
STEP: creating a claim
Jun 13 16:34:33.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6w8f
STEP: Checking for subpath error in container status
Jun 13 16:34:43.174: INFO: Deleting pod "pod-subpath-test-dynamicpv-6w8f" in namespace "provisioning-7192"
Jun 13 16:34:43.207: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6w8f" to be fully deleted
STEP: Deleting pod
Jun 13 16:34:49.275: INFO: Deleting pod "pod-subpath-test-dynamicpv-6w8f" in namespace "provisioning-7192"
STEP: Deleting pvc
Jun 13 16:34:49.367: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com7ch6m"
... skipping 12 lines ...

• [SLOW TEST:36.842 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XAbxy8blG/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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 175 lines ...
Jun 13 16:33:55.267: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3809vxbfl
STEP: creating a claim
Jun 13 16:33:55.300: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mbgb
STEP: Creating a pod to test atomic-volume-subpath
Jun 13 16:33:55.397: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mbgb" in namespace "provisioning-3809" to be "Succeeded or Failed"
Jun 13 16:33:55.429: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 31.190953ms
Jun 13 16:33:57.461: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063309652s
Jun 13 16:33:59.493: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0953058s
Jun 13 16:34:01.524: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127141628s
Jun 13 16:34:03.556: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159150904s
Jun 13 16:34:05.590: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192236475s
... skipping 19 lines ...
Jun 13 16:34:46.253: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Running", Reason="", readiness=true. Elapsed: 50.856064107s
Jun 13 16:34:48.285: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Running", Reason="", readiness=true. Elapsed: 52.887673761s
Jun 13 16:34:50.317: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Running", Reason="", readiness=true. Elapsed: 54.919930467s
Jun 13 16:34:52.349: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Running", Reason="", readiness=true. Elapsed: 56.951379104s
Jun 13 16:34:54.381: INFO: Pod "pod-subpath-test-dynamicpv-mbgb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.983913072s
STEP: Saw pod success
Jun 13 16:34:54.381: INFO: Pod "pod-subpath-test-dynamicpv-mbgb" satisfied condition "Succeeded or Failed"
Jun 13 16:34:54.413: INFO: Trying to get logs from node ip-172-20-52-62.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-mbgb container test-container-subpath-dynamicpv-mbgb: <nil>
STEP: delete the pod
Jun 13 16:34:54.483: INFO: Waiting for pod pod-subpath-test-dynamicpv-mbgb to disappear
Jun 13 16:34:54.515: INFO: Pod pod-subpath-test-dynamicpv-mbgb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mbgb
Jun 13 16:34:54.515: INFO: Deleting pod "pod-subpath-test-dynamicpv-mbgb" in namespace "provisioning-3809"
... skipping 319 lines ...
Jun 13 16:34:37.265: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9294-e2e-scg89x4
STEP: creating a claim
Jun 13 16:34:37.301: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-22lx
STEP: Creating a pod to test subpath
Jun 13 16:34:37.410: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-22lx" in namespace "provisioning-9294" to be "Succeeded or Failed"
Jun 13 16:34:37.443: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.203647ms
Jun 13 16:34:39.475: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064884449s
Jun 13 16:34:41.507: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096770324s
Jun 13 16:34:43.541: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131297837s
Jun 13 16:34:45.575: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.164793509s
Jun 13 16:34:47.606: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.196649645s
Jun 13 16:34:49.640: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.229905529s
Jun 13 16:34:51.673: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.262890166s
Jun 13 16:34:53.705: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.294791907s
Jun 13 16:34:55.736: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.326504066s
Jun 13 16:34:57.768: INFO: Pod "pod-subpath-test-dynamicpv-22lx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.358247407s
STEP: Saw pod success
Jun 13 16:34:57.768: INFO: Pod "pod-subpath-test-dynamicpv-22lx" satisfied condition "Succeeded or Failed"
Jun 13 16:34:57.800: INFO: Trying to get logs from node ip-172-20-52-220.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-22lx container test-container-subpath-dynamicpv-22lx: <nil>
STEP: delete the pod
Jun 13 16:34:57.874: INFO: Waiting for pod pod-subpath-test-dynamicpv-22lx to disappear
Jun 13 16:34:57.907: INFO: Pod pod-subpath-test-dynamicpv-22lx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-22lx
Jun 13 16:34:57.907: INFO: Deleting pod "pod-subpath-test-dynamicpv-22lx" in namespace "provisioning-9294"
... skipping 96 lines ...
Jun 13 16:34:22.460: INFO: Creating resource for dynamic PV
Jun 13 16:34:22.461: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9156-e2e-scctp9j
STEP: creating a claim
Jun 13 16:34:22.494: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9156
Jun 13 16:34:22.592: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9156" in namespace "provisioning-9156" to be "Succeeded or Failed"
Jun 13 16:34:22.625: INFO: Pod "volume-prep-provisioning-9156": Phase="Pending", Reason="", readiness=false. Elapsed: 33.09086ms
Jun 13 16:34:24.658: INFO: Pod "volume-prep-provisioning-9156": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065608298s
Jun 13 16:34:26.690: INFO: Pod "volume-prep-provisioning-9156": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097387837s
Jun 13 16:34:28.722: INFO: Pod "volume-prep-provisioning-9156": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130159614s
Jun 13 16:34:30.755: INFO: Pod "volume-prep-provisioning-9156": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162520044s
Jun 13 16:34:32.792: INFO: Pod "volume-prep-provisioning-9156": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.199511373s
STEP: Saw pod success
Jun 13 16:34:32.792: INFO: Pod "volume-prep-provisioning-9156" satisfied condition "Succeeded or Failed"
Jun 13 16:34:32.792: INFO: Deleting pod "volume-prep-provisioning-9156" in namespace "provisioning-9156"
Jun 13 16:34:32.827: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9156" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-rxtv
STEP: Checking for subpath error in container status
Jun 13 16:35:06.957: INFO: Deleting pod "pod-subpath-test-dynamicpv-rxtv" in namespace "provisioning-9156"
Jun 13 16:35:06.994: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rxtv" to be fully deleted
STEP: Deleting pod
Jun 13 16:35:07.027: INFO: Deleting pod "pod-subpath-test-dynamicpv-rxtv" in namespace "provisioning-9156"
STEP: Deleting pvc
Jun 13 16:35:07.122: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfrxcx"
... skipping 546 lines ...
Jun 13 16:34:20.638: INFO: Creating resource for dynamic PV
Jun 13 16:34:20.638: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9311-e2e-schtqhx
STEP: creating a claim
Jun 13 16:34:20.668: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 16:34:20.767: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-q4tlg" in namespace "snapshotting-9311" to be "Succeeded or Failed"
Jun 13 16:34:20.797: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 30.164092ms
Jun 13 16:34:22.830: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062335744s
Jun 13 16:34:24.860: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092633837s
Jun 13 16:34:26.891: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123198803s
Jun 13 16:34:28.922: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154491911s
Jun 13 16:34:30.953: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185884951s
Jun 13 16:34:32.984: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.216609126s
Jun 13 16:34:35.015: INFO: Pod "pvc-snapshottable-tester-q4tlg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.247459227s
STEP: Saw pod success
Jun 13 16:34:35.015: INFO: Pod "pvc-snapshottable-tester-q4tlg" satisfied condition "Succeeded or Failed"
Jun 13 16:34:35.078: INFO: Pod pvc-snapshottable-tester-q4tlg has the following logs: 
Jun 13 16:34:35.078: INFO: Deleting pod "pvc-snapshottable-tester-q4tlg" in namespace "snapshotting-9311"
Jun 13 16:34:35.113: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-q4tlg" to be fully deleted
Jun 13 16:34:35.143: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comkd6f6] to have phase Bound
Jun 13 16:34:35.174: INFO: PersistentVolumeClaim ebs.csi.aws.comkd6f6 found and phase=Bound (30.587957ms)
STEP: [init] checking the claim
... skipping 58 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XAbxy8blG/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 13 16:35:36.825: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-ct29g" in namespace "snapshotting-9311" to be "Succeeded or Failed"
Jun 13 16:35:36.856: INFO: Pod "pvc-snapshottable-data-tester-ct29g": Phase="Pending", Reason="", readiness=false. Elapsed: 30.672507ms
Jun 13 16:35:38.888: INFO: Pod "pvc-snapshottable-data-tester-ct29g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062036765s
Jun 13 16:35:40.919: INFO: Pod "pvc-snapshottable-data-tester-ct29g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0931511s
Jun 13 16:35:42.950: INFO: Pod "pvc-snapshottable-data-tester-ct29g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.124638691s
STEP: Saw pod success
Jun 13 16:35:42.950: INFO: Pod "pvc-snapshottable-data-tester-ct29g" satisfied condition "Succeeded or Failed"
Jun 13 16:35:43.019: INFO: Pod pvc-snapshottable-data-tester-ct29g has the following logs: 
Jun 13 16:35:43.019: INFO: Deleting pod "pvc-snapshottable-data-tester-ct29g" in namespace "snapshotting-9311"
Jun 13 16:35:43.067: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-ct29g" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 16:35:53.220: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9311 exec restored-pvc-tester-z5lhs --namespace=snapshotting-9311 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun 13 16:36:18.599: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:19.631: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:20.663: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:21.695: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:22.727: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:23.765: INFO: volumesnapshotcontents pre-provisioned-snapcontent-784df0e5-1806-4f8a-abee-375593c4a55c has been found and is not deleted
Jun 13 16:36:24.765: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 13 16:36:24.798: INFO: Pod restored-pvc-tester-z5lhs has the following logs: 
Jun 13 16:36:24.798: INFO: Deleting pod "restored-pvc-tester-z5lhs" in namespace "snapshotting-9311"
Jun 13 16:36:24.830: INFO: Wait up to 5m0s for pod "restored-pvc-tester-z5lhs" to be fully deleted
Jun 13 16:37:00.892: INFO: deleting claim "snapshotting-9311"/"pvc-9pfzv"
... skipping 32 lines ...
        /tmp/kops.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


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

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Pre-provisioned 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.XAbxy8blG/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

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


Ginkgo ran 1 suite in 11m1.167626733s
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
I0613 16:37:08.497063   26908 app.go:59] RunDir for this run: "/logs/artifacts/3b804f4d-cc61-11eb-ab6f-62c732df09e9"
I0613 16:37:08.498164   26908 app.go:90] ID for this run: "3b804f4d-cc61-11eb-ab6f-62c732df09e9"
I0613 16:37:08.498200   26908 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
I0613 16:37:08.513230   26914 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1513 lines ...