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

No Test Failures!


Error lines from build-log.txt

... skipping 488 lines ...
I0607 16:07:02.461120   11678 up.go:43] Cleaning up any leaked resources from previous cluster
I0607 16:07:02.461139   11678 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
I0607 16:07:02.474671   11684 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 16:07:02.474746   11684 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0607 16:07:02.963702   11678 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0607 16:07:02.963738   11678 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
I0607 16:07:02.979112   11694 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 16:07:02.979216   11694 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0607 16:07:03.475207   11678 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/07 16:07:03 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
I0607 16:07:03.484543   11678 http.go:37] curl https://ip.jsb.workers.dev
I0607 16:07:03.625395   11678 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.232.62.107/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-1a --master-size c5.large
I0607 16:07:03.640212   11708 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 16:07:03.640988   11708 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0607 16:07:03.681549   11708 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0607 16:07:04.308053   11708 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 40 lines ...

I0607 16:07:30.045668   11678 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
I0607 16:07:30.060390   11728 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 16:07:30.060932   11728 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0607 16:07:31.211600   11728 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:07:41.249176   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:07:51.281323   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
W0607 16:08:01.303281   11728 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:08:11.336754   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:08:21.380172   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:08:31.429421   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:08:41.464554   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:08:51.495549   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:01.543606   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:11.593662   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:21.622969   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:31.661027   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:41.695537   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:09:51.783792   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:01.849852   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:11.901507   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:21.947546   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:31.980361   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:42.015044   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:10:52.045577   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:02.075110   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:12.116622   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:22.160609   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:32.193239   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:42.241961   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:11:52.271328   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:12:02.319806   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-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
W0607 16:12:12.350563   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 12 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-8sp8f		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-8sp8f" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-tnp4n		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-tnp4n" is pending

Validation Failed
W0607 16:12:24.846569   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:12:35.862699   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:12:47.052295   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:12:58.410000   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:13:09.443205   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:13:20.499608   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:13:31.551745   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:13:42.627245   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:13:53.664767   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

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

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:16:06.150596   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:16:17.651209   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:16:28.779969   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:16:39.812777   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:16:50.839644   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:01.843590   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:12.901246   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:24.006655   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:35.044605   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:46.081508   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:17:57.354631   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:18:08.363574   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:18:19.424428   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:18:30.495070   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:18:41.573821   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:18:52.493751   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:19:03.534209   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:19:14.598123   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0f5255f3084a895d8					machine "i-0f5255f3084a895d8" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-bh4pr	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-bh4pr" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending

Validation Failed
W0607 16:19:26.637836   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-65dzw				system-node-critical pod "ebs-csi-node-65dzw" is pending
Pod	kube-system/ebs-csi-node-78965				system-node-critical pod "ebs-csi-node-78965" is pending
Pod	kube-system/ebs-csi-node-jsgrt				system-node-critical pod "ebs-csi-node-jsgrt" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-74.ec2.internal	system-node-critical pod "kube-proxy-ip-172-20-51-74.ec2.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-140.ec2.internal	system-node-critical pod "kube-proxy-ip-172-20-56-140.ec2.internal" is pending

Validation Failed
W0607 16:19:37.700599   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 18 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-bsvdr	system-cluster-critical pod "cert-manager-webhook-7bbf67968-bsvdr" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-gk4dl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gk4dl" is pending
Pod	kube-system/coredns-f45c4bf76-hvg6c			system-cluster-critical pod "coredns-f45c4bf76-hvg6c" is pending
Pod	kube-system/ebs-csi-node-65dzw				system-node-critical pod "ebs-csi-node-65dzw" is pending
Pod	kube-system/ebs-csi-node-jsgrt				system-node-critical pod "ebs-csi-node-jsgrt" is pending

Validation Failed
W0607 16:19:48.687628   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-g2lqj	system-node-critical pod "calico-node-g2lqj" is not ready (calico-node)
Pod	kube-system/calico-node-t7hkq	system-node-critical pod "calico-node-t7hkq" is not ready (calico-node)
Pod	kube-system/calico-node-wf8rn	system-node-critical pod "calico-node-wf8rn" is not ready (calico-node)
Pod	kube-system/calico-node-xkjvz	system-node-critical pod "calico-node-xkjvz" is not ready (calico-node)

Validation Failed
W0607 16:19:59.696722   11728 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 94 lines ...

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

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

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

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


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 12 lines ...
Jun  7 16:23:15.844: INFO: Creating resource for dynamic PV
Jun  7 16:23:15.845: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-600-e2e-sc87bmw
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  7 16:23:15.945: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 16:23:16.019: INFO: Error updating pvc ebs.csi.aws.com2bmlx: PersistentVolumeClaim "ebs.csi.aws.com2bmlx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-600-e2e-sc87bmw",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  7 16:23:46.150: INFO: Error updating pvc ebs.csi.aws.com2bmlx: PersistentVolumeClaim "ebs.csi.aws.com2bmlx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 154 lines ...
Jun  7 16:23:16.011: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6801-e2e-scm7kqv
STEP: creating a claim
Jun  7 16:23:16.043: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8gxs
STEP: Creating a pod to test subpath
Jun  7 16:23:16.151: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8gxs" in namespace "provisioning-6801" to be "Succeeded or Failed"
Jun  7 16:23:16.182: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 31.527484ms
Jun  7 16:23:18.216: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06552254s
Jun  7 16:23:20.248: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096693748s
Jun  7 16:23:22.279: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128442205s
Jun  7 16:23:24.310: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15962371s
Jun  7 16:23:26.345: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194161416s
Jun  7 16:23:28.379: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.227857966s
Jun  7 16:23:30.410: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.258710645s
Jun  7 16:23:32.441: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.29039124s
Jun  7 16:23:34.474: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Pending", Reason="", readiness=false. Elapsed: 18.323426249s
Jun  7 16:23:36.505: INFO: Pod "pod-subpath-test-dynamicpv-8gxs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.354223055s
STEP: Saw pod success
Jun  7 16:23:36.505: INFO: Pod "pod-subpath-test-dynamicpv-8gxs" satisfied condition "Succeeded or Failed"
Jun  7 16:23:36.536: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod pod-subpath-test-dynamicpv-8gxs container test-container-volume-dynamicpv-8gxs: <nil>
STEP: delete the pod
Jun  7 16:23:36.612: INFO: Waiting for pod pod-subpath-test-dynamicpv-8gxs to disappear
Jun  7 16:23:36.643: INFO: Pod pod-subpath-test-dynamicpv-8gxs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8gxs
Jun  7 16:23:36.643: INFO: Deleting pod "pod-subpath-test-dynamicpv-8gxs" in namespace "provisioning-6801"
... skipping 27 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:23:19.421: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  7 16:23:20.069: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:23:20.069: INFO: Creating resource for dynamic PV
Jun  7 16:23:20.069: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3243cx657
STEP: creating a claim
Jun  7 16:23:20.106: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-v7mr
STEP: Checking for subpath error in container status
Jun  7 16:23:52.276: INFO: Deleting pod "pod-subpath-test-dynamicpv-v7mr" in namespace "provisioning-3243"
Jun  7 16:23:52.309: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-v7mr" to be fully deleted
STEP: Deleting pod
Jun  7 16:23:58.372: INFO: Deleting pod "pod-subpath-test-dynamicpv-v7mr" in namespace "provisioning-3243"
STEP: Deleting pvc
Jun  7 16:23:58.466: INFO: Deleting PersistentVolumeClaim "awszvgw5"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:24:13.725: INFO: >>> kubeConfig: /root/.kube/config
... skipping 34 lines ...
Jun  7 16:23:14.492: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9474-e2e-sc5x629
STEP: creating a claim
Jun  7 16:23:14.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2dz2
STEP: Creating a pod to test exec-volume-test
Jun  7 16:23:14.620: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2dz2" in namespace "volume-9474" to be "Succeeded or Failed"
Jun  7 16:23:14.653: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.429516ms
Jun  7 16:23:16.689: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069560746s
Jun  7 16:23:18.740: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120208615s
Jun  7 16:23:20.777: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.15698482s
Jun  7 16:23:22.809: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.188838029s
Jun  7 16:23:24.840: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220216588s
... skipping 4 lines ...
Jun  7 16:23:35.000: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.380244222s
Jun  7 16:23:37.033: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.412769415s
Jun  7 16:23:39.065: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 24.44513884s
Jun  7 16:23:41.112: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Pending", Reason="", readiness=false. Elapsed: 26.492649204s
Jun  7 16:23:43.144: INFO: Pod "exec-volume-test-dynamicpv-2dz2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.524601646s
STEP: Saw pod success
Jun  7 16:23:43.144: INFO: Pod "exec-volume-test-dynamicpv-2dz2" satisfied condition "Succeeded or Failed"
Jun  7 16:23:43.175: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod exec-volume-test-dynamicpv-2dz2 container exec-container-dynamicpv-2dz2: <nil>
STEP: delete the pod
Jun  7 16:23:43.249: INFO: Waiting for pod exec-volume-test-dynamicpv-2dz2 to disappear
Jun  7 16:23:43.280: INFO: Pod exec-volume-test-dynamicpv-2dz2 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2dz2
Jun  7 16:23:43.280: INFO: Deleting pod "exec-volume-test-dynamicpv-2dz2" in namespace "volume-9474"
... skipping 68 lines ...
Jun  7 16:23:13.672: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1087-e2e-sczp8dz
STEP: creating a claim
Jun  7 16:23:13.711: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jn2b
STEP: Creating a pod to test subpath
Jun  7 16:23:13.832: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jn2b" in namespace "provisioning-1087" to be "Succeeded or Failed"
Jun  7 16:23:13.869: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 36.298166ms
Jun  7 16:23:15.904: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071299145s
Jun  7 16:23:17.935: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102791169s
Jun  7 16:23:19.967: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13431645s
Jun  7 16:23:21.998: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.166226259s
Jun  7 16:23:24.030: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.198118535s
... skipping 5 lines ...
Jun  7 16:23:36.223: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 22.390478466s
Jun  7 16:23:38.254: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 24.421332484s
Jun  7 16:23:40.286: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 26.453976444s
Jun  7 16:23:42.323: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Pending", Reason="", readiness=false. Elapsed: 28.490561183s
Jun  7 16:23:44.354: INFO: Pod "pod-subpath-test-dynamicpv-jn2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.5215709s
STEP: Saw pod success
Jun  7 16:23:44.354: INFO: Pod "pod-subpath-test-dynamicpv-jn2b" satisfied condition "Succeeded or Failed"
Jun  7 16:23:44.384: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod pod-subpath-test-dynamicpv-jn2b container test-container-subpath-dynamicpv-jn2b: <nil>
STEP: delete the pod
Jun  7 16:23:44.461: INFO: Waiting for pod pod-subpath-test-dynamicpv-jn2b to disappear
Jun  7 16:23:44.491: INFO: Pod pod-subpath-test-dynamicpv-jn2b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jn2b
Jun  7 16:23:44.491: INFO: Deleting pod "pod-subpath-test-dynamicpv-jn2b" in namespace "provisioning-1087"
... skipping 197 lines ...
Jun  7 16:23:17.460: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-15512hsb9
STEP: creating a claim
Jun  7 16:23:17.491: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ch66
STEP: Creating a pod to test subpath
Jun  7 16:23:17.586: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ch66" in namespace "provisioning-1551" to be "Succeeded or Failed"
Jun  7 16:23:17.620: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 33.287513ms
Jun  7 16:23:19.652: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065327732s
Jun  7 16:23:21.682: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095876596s
Jun  7 16:23:23.713: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126850933s
Jun  7 16:23:25.744: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157891989s
Jun  7 16:23:27.776: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189980207s
... skipping 7 lines ...
Jun  7 16:23:44.023: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 26.436773478s
Jun  7 16:23:46.055: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 28.468075613s
Jun  7 16:23:48.086: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 30.499373919s
Jun  7 16:23:50.116: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 32.529819531s
Jun  7 16:23:52.148: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.561433646s
STEP: Saw pod success
Jun  7 16:23:52.148: INFO: Pod "pod-subpath-test-dynamicpv-ch66" satisfied condition "Succeeded or Failed"
Jun  7 16:23:52.178: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-ch66 container test-container-subpath-dynamicpv-ch66: <nil>
STEP: delete the pod
Jun  7 16:23:52.252: INFO: Waiting for pod pod-subpath-test-dynamicpv-ch66 to disappear
Jun  7 16:23:52.283: INFO: Pod pod-subpath-test-dynamicpv-ch66 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ch66
Jun  7 16:23:52.283: INFO: Deleting pod "pod-subpath-test-dynamicpv-ch66" in namespace "provisioning-1551"
STEP: Creating pod pod-subpath-test-dynamicpv-ch66
STEP: Creating a pod to test subpath
Jun  7 16:23:52.351: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ch66" in namespace "provisioning-1551" to be "Succeeded or Failed"
Jun  7 16:23:52.381: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 30.502794ms
Jun  7 16:23:54.412: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061432989s
Jun  7 16:23:56.444: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09313589s
Jun  7 16:23:58.474: INFO: Pod "pod-subpath-test-dynamicpv-ch66": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.12358574s
STEP: Saw pod success
Jun  7 16:23:58.474: INFO: Pod "pod-subpath-test-dynamicpv-ch66" satisfied condition "Succeeded or Failed"
Jun  7 16:23:58.507: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-ch66 container test-container-subpath-dynamicpv-ch66: <nil>
STEP: delete the pod
Jun  7 16:23:58.576: INFO: Waiting for pod pod-subpath-test-dynamicpv-ch66 to disappear
Jun  7 16:23:58.606: INFO: Pod pod-subpath-test-dynamicpv-ch66 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ch66
Jun  7 16:23:58.606: INFO: Deleting pod "pod-subpath-test-dynamicpv-ch66" in namespace "provisioning-1551"
... skipping 219 lines ...
Jun  7 16:23:14.442: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-131-e2e-scjqx6w
STEP: creating a claim
Jun  7 16:23:14.474: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s5k5
STEP: Creating a pod to test subpath
Jun  7 16:23:14.570: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s5k5" in namespace "provisioning-131" to be "Succeeded or Failed"
Jun  7 16:23:14.601: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 31.02945ms
Jun  7 16:23:16.633: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063082486s
Jun  7 16:23:18.674: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103595276s
Jun  7 16:23:20.708: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137770821s
Jun  7 16:23:22.744: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.174209348s
Jun  7 16:23:24.775: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.205573978s
... skipping 8 lines ...
Jun  7 16:23:43.065: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 28.495453664s
Jun  7 16:23:45.097: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 30.526716261s
Jun  7 16:23:47.128: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.558204389s
Jun  7 16:23:49.160: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.590473326s
Jun  7 16:23:51.192: INFO: Pod "pod-subpath-test-dynamicpv-s5k5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.621641872s
STEP: Saw pod success
Jun  7 16:23:51.192: INFO: Pod "pod-subpath-test-dynamicpv-s5k5" satisfied condition "Succeeded or Failed"
Jun  7 16:23:51.227: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-s5k5 container test-container-volume-dynamicpv-s5k5: <nil>
STEP: delete the pod
Jun  7 16:23:51.308: INFO: Waiting for pod pod-subpath-test-dynamicpv-s5k5 to disappear
Jun  7 16:23:51.339: INFO: Pod pod-subpath-test-dynamicpv-s5k5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s5k5
Jun  7 16:23:51.339: INFO: Deleting pod "pod-subpath-test-dynamicpv-s5k5" in namespace "provisioning-131"
... skipping 264 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 142 lines ...
Jun  7 16:23:13.622: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6030pmtn4
STEP: creating a claim
Jun  7 16:23:13.660: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-scv9
STEP: Creating a pod to test atomic-volume-subpath
Jun  7 16:23:13.778: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-scv9" in namespace "provisioning-6030" to be "Succeeded or Failed"
Jun  7 16:23:13.814: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 35.131948ms
Jun  7 16:23:15.845: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066503742s
Jun  7 16:23:17.880: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101893283s
Jun  7 16:23:19.911: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.133013985s
Jun  7 16:23:21.944: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16514665s
Jun  7 16:23:23.975: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.196803785s
... skipping 18 lines ...
Jun  7 16:24:02.579: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Running", Reason="", readiness=true. Elapsed: 48.800681144s
Jun  7 16:24:04.610: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Running", Reason="", readiness=true. Elapsed: 50.831931931s
Jun  7 16:24:06.642: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Running", Reason="", readiness=true. Elapsed: 52.863907443s
Jun  7 16:24:08.674: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Running", Reason="", readiness=true. Elapsed: 54.895248697s
Jun  7 16:24:10.705: INFO: Pod "pod-subpath-test-dynamicpv-scv9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.92663356s
STEP: Saw pod success
Jun  7 16:24:10.705: INFO: Pod "pod-subpath-test-dynamicpv-scv9" satisfied condition "Succeeded or Failed"
Jun  7 16:24:10.736: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod pod-subpath-test-dynamicpv-scv9 container test-container-subpath-dynamicpv-scv9: <nil>
STEP: delete the pod
Jun  7 16:24:10.805: INFO: Waiting for pod pod-subpath-test-dynamicpv-scv9 to disappear
Jun  7 16:24:10.835: INFO: Pod pod-subpath-test-dynamicpv-scv9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-scv9
Jun  7 16:24:10.835: INFO: Deleting pod "pod-subpath-test-dynamicpv-scv9" in namespace "provisioning-6030"
... skipping 241 lines ...
Jun  7 16:23:17.312: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-32-e2e-sc94kdc
STEP: creating a claim
Jun  7 16:23:17.345: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kv5k
STEP: Creating a pod to test atomic-volume-subpath
Jun  7 16:23:17.442: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kv5k" in namespace "provisioning-32" to be "Succeeded or Failed"
Jun  7 16:23:17.474: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 31.255553ms
Jun  7 16:23:19.507: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064621038s
Jun  7 16:23:21.539: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096323552s
Jun  7 16:23:23.570: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127829359s
Jun  7 16:23:25.601: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159150208s
Jun  7 16:23:27.633: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190322835s
... skipping 11 lines ...
Jun  7 16:23:52.022: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Running", Reason="", readiness=true. Elapsed: 34.579944978s
Jun  7 16:23:54.054: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Running", Reason="", readiness=true. Elapsed: 36.612147286s
Jun  7 16:23:56.086: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Running", Reason="", readiness=true. Elapsed: 38.643241108s
Jun  7 16:23:58.117: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Running", Reason="", readiness=true. Elapsed: 40.674633931s
Jun  7 16:24:00.150: INFO: Pod "pod-subpath-test-dynamicpv-kv5k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.707461246s
STEP: Saw pod success
Jun  7 16:24:00.150: INFO: Pod "pod-subpath-test-dynamicpv-kv5k" satisfied condition "Succeeded or Failed"
Jun  7 16:24:00.181: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod pod-subpath-test-dynamicpv-kv5k container test-container-subpath-dynamicpv-kv5k: <nil>
STEP: delete the pod
Jun  7 16:24:00.253: INFO: Waiting for pod pod-subpath-test-dynamicpv-kv5k to disappear
Jun  7 16:24:00.283: INFO: Pod pod-subpath-test-dynamicpv-kv5k no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kv5k
Jun  7 16:24:00.283: INFO: Deleting pod "pod-subpath-test-dynamicpv-kv5k" in namespace "provisioning-32"
... skipping 66 lines ...
Jun  7 16:23:13.695: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8807-e2e-scl4748
STEP: creating a claim
Jun  7 16:23:13.728: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-tqh6
STEP: Creating a pod to test exec-volume-test
Jun  7 16:23:13.864: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-tqh6" in namespace "volume-8807" to be "Succeeded or Failed"
Jun  7 16:23:13.898: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 33.707455ms
Jun  7 16:23:15.929: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064703714s
Jun  7 16:23:17.960: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095837466s
Jun  7 16:23:19.992: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1278155s
Jun  7 16:23:22.024: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159391013s
Jun  7 16:23:24.056: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191580406s
Jun  7 16:23:26.095: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.230142627s
Jun  7 16:23:28.126: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.261266202s
Jun  7 16:23:30.158: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.293720919s
Jun  7 16:23:32.190: INFO: Pod "exec-volume-test-dynamicpv-tqh6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.32596035s
STEP: Saw pod success
Jun  7 16:23:32.190: INFO: Pod "exec-volume-test-dynamicpv-tqh6" satisfied condition "Succeeded or Failed"
Jun  7 16:23:32.221: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod exec-volume-test-dynamicpv-tqh6 container exec-container-dynamicpv-tqh6: <nil>
STEP: delete the pod
Jun  7 16:23:32.319: INFO: Waiting for pod exec-volume-test-dynamicpv-tqh6 to disappear
Jun  7 16:23:32.351: INFO: Pod exec-volume-test-dynamicpv-tqh6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-tqh6
Jun  7 16:23:32.351: INFO: Deleting pod "exec-volume-test-dynamicpv-tqh6" in namespace "volume-8807"
... skipping 304 lines ...
Jun  7 16:23:54.114: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5247j7f6f
STEP: creating a claim
Jun  7 16:23:54.146: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-trx2
STEP: Creating a pod to test multi_subpath
Jun  7 16:23:54.241: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-trx2" in namespace "provisioning-5247" to be "Succeeded or Failed"
Jun  7 16:23:54.272: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.719507ms
Jun  7 16:23:56.303: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062504699s
Jun  7 16:23:58.335: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093850771s
Jun  7 16:24:00.366: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124805677s
Jun  7 16:24:02.397: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155902839s
Jun  7 16:24:04.429: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187687529s
... skipping 2 lines ...
Jun  7 16:24:10.523: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.281714611s
Jun  7 16:24:12.554: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.313232105s
Jun  7 16:24:14.586: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.345258658s
Jun  7 16:24:16.617: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.376544352s
Jun  7 16:24:18.650: INFO: Pod "pod-subpath-test-dynamicpv-trx2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.408722462s
STEP: Saw pod success
Jun  7 16:24:18.650: INFO: Pod "pod-subpath-test-dynamicpv-trx2" satisfied condition "Succeeded or Failed"
Jun  7 16:24:18.681: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod pod-subpath-test-dynamicpv-trx2 container test-container-subpath-dynamicpv-trx2: <nil>
STEP: delete the pod
Jun  7 16:24:18.768: INFO: Waiting for pod pod-subpath-test-dynamicpv-trx2 to disappear
Jun  7 16:24:18.798: INFO: Pod pod-subpath-test-dynamicpv-trx2 no longer exists
STEP: Deleting pod
Jun  7 16:24:18.798: INFO: Deleting pod "pod-subpath-test-dynamicpv-trx2" in namespace "provisioning-5247"
... skipping 682 lines ...
Jun  7 16:23:15.240: INFO: Creating resource for dynamic PV
Jun  7 16:23:15.240: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-36-e2e-scfmhrw
STEP: creating a claim
Jun  7 16:23:15.272: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-36
Jun  7 16:23:15.366: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-36" in namespace "provisioning-36" to be "Succeeded or Failed"
Jun  7 16:23:15.397: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 30.18274ms
Jun  7 16:23:17.428: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061604969s
Jun  7 16:23:19.471: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104906015s
Jun  7 16:23:21.506: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139606014s
Jun  7 16:23:23.540: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173281905s
Jun  7 16:23:25.570: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204130956s
... skipping 6 lines ...
Jun  7 16:23:39.794: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 24.42809346s
Jun  7 16:23:41.826: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 26.459985908s
Jun  7 16:23:43.858: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 28.491510053s
Jun  7 16:23:45.889: INFO: Pod "volume-prep-provisioning-36": Phase="Pending", Reason="", readiness=false. Elapsed: 30.52250599s
Jun  7 16:23:47.920: INFO: Pod "volume-prep-provisioning-36": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.554019188s
STEP: Saw pod success
Jun  7 16:23:47.920: INFO: Pod "volume-prep-provisioning-36" satisfied condition "Succeeded or Failed"
Jun  7 16:23:47.920: INFO: Deleting pod "volume-prep-provisioning-36" in namespace "provisioning-36"
Jun  7 16:23:47.957: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-36" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-xxsx
STEP: Checking for subpath error in container status
Jun  7 16:24:22.086: INFO: Deleting pod "pod-subpath-test-dynamicpv-xxsx" in namespace "provisioning-36"
Jun  7 16:24:22.126: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xxsx" to be fully deleted
STEP: Deleting pod
Jun  7 16:24:22.157: INFO: Deleting pod "pod-subpath-test-dynamicpv-xxsx" in namespace "provisioning-36"
STEP: Deleting pvc
Jun  7 16:24:22.249: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4997v"
... skipping 151 lines ...
Jun  7 16:24:27.042: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5710tnkw2
STEP: creating a claim
Jun  7 16:24:27.074: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bdxb
STEP: Creating a pod to test exec-volume-test
Jun  7 16:24:27.172: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bdxb" in namespace "volume-5710" to be "Succeeded or Failed"
Jun  7 16:24:27.203: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.829589ms
Jun  7 16:24:29.247: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075604057s
Jun  7 16:24:31.280: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108553619s
Jun  7 16:24:33.312: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140129701s
Jun  7 16:24:35.345: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173228058s
Jun  7 16:24:37.377: INFO: Pod "exec-volume-test-dynamicpv-bdxb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.205724751s
STEP: Saw pod success
Jun  7 16:24:37.378: INFO: Pod "exec-volume-test-dynamicpv-bdxb" satisfied condition "Succeeded or Failed"
Jun  7 16:24:37.409: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod exec-volume-test-dynamicpv-bdxb container exec-container-dynamicpv-bdxb: <nil>
STEP: delete the pod
Jun  7 16:24:37.480: INFO: Waiting for pod exec-volume-test-dynamicpv-bdxb to disappear
Jun  7 16:24:37.513: INFO: Pod exec-volume-test-dynamicpv-bdxb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bdxb
Jun  7 16:24:37.513: INFO: Deleting pod "exec-volume-test-dynamicpv-bdxb" in namespace "volume-5710"
... skipping 316 lines ...
Jun  7 16:23:15.942: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-6692-e2e-scjcp9n      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-6692    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-6692-e2e-scjcp9n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6692    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-6692-e2e-scjcp9n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6692    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-6692-e2e-scjcp9n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-6692-e2e-scjcp9n    6059966f-a5e2-4dfe-a081-b31ab3bfd5c1 3263 0 2021-06-07 16:23:15 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-07 16:23:15 +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-bv9nf pvc- provisioning-6692  5e4d29a3-61b3-4bee-b62d-2871b33c1bed 3275 0 2021-06-07 16:23:16 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-07 16:23:16 +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-6692-e2e-scjcp9n,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-f1933fb5-fa20-449c-ab2f-0f807361dccd in namespace provisioning-6692
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  7 16:23:42.310: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-x2x6g" in namespace "provisioning-6692" to be "Succeeded or Failed"
Jun  7 16:23:42.341: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 30.897774ms
Jun  7 16:23:44.371: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061660729s
Jun  7 16:23:46.405: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094895408s
Jun  7 16:23:48.436: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125947684s
Jun  7 16:23:50.467: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157619677s
Jun  7 16:23:52.498: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188787679s
... skipping 23 lines ...
Jun  7 16:24:41.294: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 58.984524861s
Jun  7 16:24:43.326: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.015974875s
Jun  7 16:24:45.358: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.047980486s
Jun  7 16:24:47.389: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.078919305s
Jun  7 16:24:49.420: INFO: Pod "pvc-volume-tester-writer-x2x6g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.110227934s
STEP: Saw pod success
Jun  7 16:24:49.420: INFO: Pod "pvc-volume-tester-writer-x2x6g" satisfied condition "Succeeded or Failed"
Jun  7 16:24:49.490: INFO: Pod pvc-volume-tester-writer-x2x6g has the following logs: 
Jun  7 16:24:49.490: INFO: Deleting pod "pvc-volume-tester-writer-x2x6g" in namespace "provisioning-6692"
Jun  7 16:24:49.528: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-x2x6g" 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-56-140.ec2.internal"
Jun  7 16:24:49.662: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-9pghp" in namespace "provisioning-6692" to be "Succeeded or Failed"
Jun  7 16:24:49.693: INFO: Pod "pvc-volume-tester-reader-9pghp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.833941ms
Jun  7 16:24:51.725: INFO: Pod "pvc-volume-tester-reader-9pghp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062933954s
Jun  7 16:24:53.757: INFO: Pod "pvc-volume-tester-reader-9pghp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.095018422s
STEP: Saw pod success
Jun  7 16:24:53.757: INFO: Pod "pvc-volume-tester-reader-9pghp" satisfied condition "Succeeded or Failed"
Jun  7 16:24:53.824: INFO: Pod pvc-volume-tester-reader-9pghp has the following logs: hello world

Jun  7 16:24:53.824: INFO: Deleting pod "pvc-volume-tester-reader-9pghp" in namespace "provisioning-6692"
Jun  7 16:24:53.862: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-9pghp" to be fully deleted
Jun  7 16:24:53.892: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-bv9nf] to have phase Bound
Jun  7 16:24:53.926: INFO: PersistentVolumeClaim pvc-bv9nf found and phase=Bound (33.080015ms)
... skipping 32 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 111 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:24:34.584: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:24:34.746: INFO: Creating resource for dynamic PV
Jun  7 16:24:34.746: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-7794-e2e-scxmgdb
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:24:40.985: INFO: Deleting pod "pod-b90ab95d-300a-4b0b-b1ee-a9bafeb06ae9" in namespace "volumemode-7794"
Jun  7 16:24:41.022: INFO: Wait up to 5m0s for pod "pod-b90ab95d-300a-4b0b-b1ee-a9bafeb06ae9" to be fully deleted
STEP: Deleting pvc
Jun  7 16:24:45.155: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comk42d4"
Jun  7 16:24:45.194: INFO: Waiting up to 5m0s for PersistentVolume pvc-ca395cb2-a50b-426f-8dd3-fa8bf76144e8 to get deleted
Jun  7 16:24:45.226: INFO: PersistentVolume pvc-ca395cb2-a50b-426f-8dd3-fa8bf76144e8 found and phase=Released (31.676554ms)
... skipping 13 lines ...

• [SLOW TEST:45.969 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 272 lines ...
Jun  7 16:24:46.518: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5792fbf2s
STEP: creating a claim
Jun  7 16:24:46.551: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2vwz
STEP: Creating a pod to test subpath
Jun  7 16:24:46.674: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2vwz" in namespace "provisioning-5792" to be "Succeeded or Failed"
Jun  7 16:24:46.704: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.335837ms
Jun  7 16:24:48.735: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061024124s
Jun  7 16:24:50.767: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093565098s
Jun  7 16:24:52.798: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124309238s
Jun  7 16:24:54.829: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154975741s
Jun  7 16:24:56.861: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186891902s
... skipping 3 lines ...
Jun  7 16:25:05.058: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.384738166s
Jun  7 16:25:07.089: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.415472029s
Jun  7 16:25:09.123: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.449387547s
Jun  7 16:25:11.154: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Pending", Reason="", readiness=false. Elapsed: 24.480496034s
Jun  7 16:25:13.187: INFO: Pod "pod-subpath-test-dynamicpv-2vwz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.512922167s
STEP: Saw pod success
Jun  7 16:25:13.187: INFO: Pod "pod-subpath-test-dynamicpv-2vwz" satisfied condition "Succeeded or Failed"
Jun  7 16:25:13.217: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-2vwz container test-container-volume-dynamicpv-2vwz: <nil>
STEP: delete the pod
Jun  7 16:25:13.289: INFO: Waiting for pod pod-subpath-test-dynamicpv-2vwz to disappear
Jun  7 16:25:13.322: INFO: Pod pod-subpath-test-dynamicpv-2vwz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2vwz
Jun  7 16:25:13.322: INFO: Deleting pod "pod-subpath-test-dynamicpv-2vwz" in namespace "provisioning-5792"
... skipping 64 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 122 lines ...
Jun  7 16:25:35.962: INFO: Waiting for pod aws-client to disappear
Jun  7 16:25:35.994: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 16:25:35.994: INFO: Deleting PersistentVolumeClaim "pvc-xjhjf"
Jun  7 16:25:36.026: INFO: Deleting PersistentVolume "aws-cwvrw"
Jun  7 16:25:36.240: INFO: Couldn't delete PD "aws://us-east-1a/vol-0a2a4bf09a15387c6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a2a4bf09a15387c6 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: ca57e077-90ca-4b58-ab86-78702dbec2c9
Jun  7 16:25:41.666: INFO: Successfully deleted PD "aws://us-east-1a/vol-0a2a4bf09a15387c6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:25:41.666: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5855" for this suite.
... skipping 150 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Jun  7 16:24:59.551: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-346d59k
STEP: creating a claim
Jun  7 16:24:59.582: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qqnk
STEP: Creating a pod to test subpath
Jun  7 16:24:59.676: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qqnk" in namespace "provisioning-34" to be "Succeeded or Failed"
Jun  7 16:24:59.706: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.153212ms
Jun  7 16:25:01.738: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061718412s
Jun  7 16:25:03.769: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093177328s
Jun  7 16:25:05.800: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12399069s
Jun  7 16:25:07.832: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155707447s
Jun  7 16:25:09.863: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.1873202s
... skipping 2 lines ...
Jun  7 16:25:15.957: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.281437126s
Jun  7 16:25:17.989: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.313000654s
Jun  7 16:25:20.021: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.345306974s
Jun  7 16:25:22.053: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.377267528s
Jun  7 16:25:24.086: INFO: Pod "pod-subpath-test-dynamicpv-qqnk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.409494302s
STEP: Saw pod success
Jun  7 16:25:24.086: INFO: Pod "pod-subpath-test-dynamicpv-qqnk" satisfied condition "Succeeded or Failed"
Jun  7 16:25:24.116: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod pod-subpath-test-dynamicpv-qqnk container test-container-subpath-dynamicpv-qqnk: <nil>
STEP: delete the pod
Jun  7 16:25:24.189: INFO: Waiting for pod pod-subpath-test-dynamicpv-qqnk to disappear
Jun  7 16:25:24.219: INFO: Pod pod-subpath-test-dynamicpv-qqnk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qqnk
Jun  7 16:25:24.220: INFO: Deleting pod "pod-subpath-test-dynamicpv-qqnk" in namespace "provisioning-34"
... skipping 497 lines ...
Jun  7 16:26:11.937: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 374 lines ...
Jun  7 16:26:05.320: INFO: Pod aws-client still exists
Jun  7 16:26:07.289: INFO: Waiting for pod aws-client to disappear
Jun  7 16:26:07.320: INFO: Pod aws-client still exists
Jun  7 16:26:09.288: INFO: Waiting for pod aws-client to disappear
Jun  7 16:26:09.319: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  7 16:26:09.693: INFO: Couldn't delete PD "aws://us-east-1a/vol-0d5b6ad1e6e4bcb67", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d5b6ad1e6e4bcb67 is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: f3795eec-cc21-42c2-a419-5222a8d6dd58
Jun  7 16:26:14.979: INFO: Successfully deleted PD "aws://us-east-1a/vol-0d5b6ad1e6e4bcb67".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:26:14.979: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5894" for this suite.
... skipping 197 lines ...
Jun  7 16:25:54.228: INFO: PersistentVolumeClaim pvc-ffmrn found but phase is Pending instead of Bound.
Jun  7 16:25:56.261: INFO: PersistentVolumeClaim pvc-ffmrn found and phase=Bound (12.226849408s)
Jun  7 16:25:56.261: INFO: Waiting up to 3m0s for PersistentVolume aws-r7db2 to have phase Bound
Jun  7 16:25:56.292: INFO: PersistentVolume aws-r7db2 found and phase=Bound (31.29871ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-rx2v
STEP: Creating a pod to test exec-volume-test
Jun  7 16:25:56.388: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-rx2v" in namespace "volume-1942" to be "Succeeded or Failed"
Jun  7 16:25:56.419: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v": Phase="Pending", Reason="", readiness=false. Elapsed: 31.394428ms
Jun  7 16:25:58.452: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064321165s
Jun  7 16:26:00.484: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095837202s
Jun  7 16:26:02.517: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128641228s
Jun  7 16:26:04.548: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.160324191s
STEP: Saw pod success
Jun  7 16:26:04.548: INFO: Pod "exec-volume-test-preprovisionedpv-rx2v" satisfied condition "Succeeded or Failed"
Jun  7 16:26:04.582: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod exec-volume-test-preprovisionedpv-rx2v container exec-container-preprovisionedpv-rx2v: <nil>
STEP: delete the pod
Jun  7 16:26:04.655: INFO: Waiting for pod exec-volume-test-preprovisionedpv-rx2v to disappear
Jun  7 16:26:04.687: INFO: Pod exec-volume-test-preprovisionedpv-rx2v no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-rx2v
Jun  7 16:26:04.687: INFO: Deleting pod "exec-volume-test-preprovisionedpv-rx2v" in namespace "volume-1942"
STEP: Deleting pv and pvc
Jun  7 16:26:04.719: INFO: Deleting PersistentVolumeClaim "pvc-ffmrn"
Jun  7 16:26:04.752: INFO: Deleting PersistentVolume "aws-r7db2"
Jun  7 16:26:05.011: INFO: Couldn't delete PD "aws://us-east-1a/vol-02f7bd51503fcdb6b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f7bd51503fcdb6b is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 4ed33285-e023-4b04-87d4-2116ad6fe481
Jun  7 16:26:10.374: INFO: Couldn't delete PD "aws://us-east-1a/vol-02f7bd51503fcdb6b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f7bd51503fcdb6b is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 302f6652-30f8-4567-bfaf-e2f1cb145687
Jun  7 16:26:15.879: INFO: Couldn't delete PD "aws://us-east-1a/vol-02f7bd51503fcdb6b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f7bd51503fcdb6b is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 973d89b6-812d-486a-ac52-035c412e6677
Jun  7 16:26:21.237: INFO: Successfully deleted PD "aws://us-east-1a/vol-02f7bd51503fcdb6b".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:26:21.237: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1942" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 355 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:25:31.887: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  7 16:25:32.044: INFO: Creating resource for dynamic PV
Jun  7 16:25:32.044: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7054-e2e-scgd8mz
STEP: creating a claim
Jun  7 16:25:32.077: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2lzs
STEP: Checking for subpath error in container status
Jun  7 16:25:58.237: INFO: Deleting pod "pod-subpath-test-dynamicpv-2lzs" in namespace "provisioning-7054"
Jun  7 16:25:58.270: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2lzs" to be fully deleted
STEP: Deleting pod
Jun  7 16:26:04.334: INFO: Deleting pod "pod-subpath-test-dynamicpv-2lzs" in namespace "provisioning-7054"
STEP: Deleting pvc
Jun  7 16:26:04.430: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5tqbf"
... skipping 15 lines ...

• [SLOW TEST:67.929 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 16:26:39.818: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 60 lines ...
Jun  7 16:26:24.279: INFO: PersistentVolumeClaim pvc-28wnw found but phase is Pending instead of Bound.
Jun  7 16:26:26.312: INFO: PersistentVolumeClaim pvc-28wnw found and phase=Bound (10.196999821s)
Jun  7 16:26:26.312: INFO: Waiting up to 3m0s for PersistentVolume aws-n2fvr to have phase Bound
Jun  7 16:26:26.342: INFO: PersistentVolume aws-n2fvr found and phase=Bound (30.576257ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-vlzb
STEP: Creating a pod to test exec-volume-test
Jun  7 16:26:26.456: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-vlzb" in namespace "volume-2198" to be "Succeeded or Failed"
Jun  7 16:26:26.487: INFO: Pod "exec-volume-test-preprovisionedpv-vlzb": Phase="Pending", Reason="", readiness=false. Elapsed: 31.177207ms
Jun  7 16:26:28.521: INFO: Pod "exec-volume-test-preprovisionedpv-vlzb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065211133s
Jun  7 16:26:30.553: INFO: Pod "exec-volume-test-preprovisionedpv-vlzb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097015674s
Jun  7 16:26:32.585: INFO: Pod "exec-volume-test-preprovisionedpv-vlzb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.129675973s
STEP: Saw pod success
Jun  7 16:26:32.585: INFO: Pod "exec-volume-test-preprovisionedpv-vlzb" satisfied condition "Succeeded or Failed"
Jun  7 16:26:32.617: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod exec-volume-test-preprovisionedpv-vlzb container exec-container-preprovisionedpv-vlzb: <nil>
STEP: delete the pod
Jun  7 16:26:32.695: INFO: Waiting for pod exec-volume-test-preprovisionedpv-vlzb to disappear
Jun  7 16:26:32.731: INFO: Pod exec-volume-test-preprovisionedpv-vlzb no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-vlzb
Jun  7 16:26:32.731: INFO: Deleting pod "exec-volume-test-preprovisionedpv-vlzb" in namespace "volume-2198"
STEP: Deleting pv and pvc
Jun  7 16:26:32.764: INFO: Deleting PersistentVolumeClaim "pvc-28wnw"
Jun  7 16:26:32.823: INFO: Deleting PersistentVolume "aws-n2fvr"
Jun  7 16:26:33.051: INFO: Couldn't delete PD "aws://us-east-1a/vol-063cecbc07179a2d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-063cecbc07179a2d8 is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 30b41fa6-a502-49b0-92df-5011cb218aec
Jun  7 16:26:38.498: INFO: Couldn't delete PD "aws://us-east-1a/vol-063cecbc07179a2d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-063cecbc07179a2d8 is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 4a54d649-515e-40d6-b0dc-651ba718c6b1
Jun  7 16:26:43.934: INFO: Couldn't delete PD "aws://us-east-1a/vol-063cecbc07179a2d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-063cecbc07179a2d8 is currently attached to i-0637bb7144cc4016d
	status code: 400, request id: 780016d6-3244-42a3-9b22-a7717d77d173
Jun  7 16:26:49.290: INFO: Successfully deleted PD "aws://us-east-1a/vol-063cecbc07179a2d8".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:26:49.290: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2198" for this suite.
... skipping 199 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:26:12.385: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  7 16:26:12.544: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:26:12.544: INFO: Creating resource for dynamic PV
Jun  7 16:26:12.544: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-465396hdl
STEP: creating a claim
Jun  7 16:26:12.575: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-668v
STEP: Checking for subpath error in container status
Jun  7 16:26:26.733: INFO: Deleting pod "pod-subpath-test-dynamicpv-668v" in namespace "provisioning-4653"
Jun  7 16:26:26.764: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-668v" to be fully deleted
STEP: Deleting pod
Jun  7 16:26:34.829: INFO: Deleting pod "pod-subpath-test-dynamicpv-668v" in namespace "provisioning-4653"
STEP: Deleting pvc
Jun  7 16:26:34.937: INFO: Deleting PersistentVolumeClaim "aws25kc5"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:26:50.120: INFO: >>> kubeConfig: /root/.kube/config
... skipping 29 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 335 lines ...
Jun  7 16:26:39.844: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 16:26:40.368: INFO: Successfully created a new PD: "aws://us-east-1a/vol-0bbf49046d20344a5".
Jun  7 16:26:40.368: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-8629
STEP: Creating a pod to test exec-volume-test
Jun  7 16:26:40.401: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-8629" in namespace "volume-2964" to be "Succeeded or Failed"
Jun  7 16:26:40.433: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Pending", Reason="", readiness=false. Elapsed: 31.963821ms
Jun  7 16:26:42.465: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064159687s
Jun  7 16:26:44.497: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096229782s
Jun  7 16:26:46.529: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128374949s
Jun  7 16:26:48.561: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160507065s
Jun  7 16:26:50.598: INFO: Pod "exec-volume-test-inlinevolume-8629": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.197133549s
STEP: Saw pod success
Jun  7 16:26:50.598: INFO: Pod "exec-volume-test-inlinevolume-8629" satisfied condition "Succeeded or Failed"
Jun  7 16:26:50.631: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod exec-volume-test-inlinevolume-8629 container exec-container-inlinevolume-8629: <nil>
STEP: delete the pod
Jun  7 16:26:50.700: INFO: Waiting for pod exec-volume-test-inlinevolume-8629 to disappear
Jun  7 16:26:50.730: INFO: Pod exec-volume-test-inlinevolume-8629 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-8629
Jun  7 16:26:50.731: INFO: Deleting pod "exec-volume-test-inlinevolume-8629" in namespace "volume-2964"
Jun  7 16:26:50.946: INFO: Couldn't delete PD "aws://us-east-1a/vol-0bbf49046d20344a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bbf49046d20344a5 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 45743ad0-0a2e-405f-afa9-494ea5983bad
Jun  7 16:26:56.264: INFO: Couldn't delete PD "aws://us-east-1a/vol-0bbf49046d20344a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bbf49046d20344a5 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 647004ea-45c9-472f-8b76-6af41da16a1e
Jun  7 16:27:01.580: INFO: Successfully deleted PD "aws://us-east-1a/vol-0bbf49046d20344a5".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:27:01.580: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2964" for this suite.
... skipping 77 lines ...
Jun  7 16:26:40.979: INFO: Waiting for pod aws-client to disappear
Jun  7 16:26:41.011: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 16:26:41.011: INFO: Deleting PersistentVolumeClaim "pvc-rt4gt"
Jun  7 16:26:41.043: INFO: Deleting PersistentVolume "aws-78mzc"
Jun  7 16:26:41.369: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c71d9029b7826fae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c71d9029b7826fae is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: 84c38277-ae74-4b65-ba21-701b4ee52205
Jun  7 16:26:46.748: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c71d9029b7826fae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c71d9029b7826fae is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: aa5ee4e5-0f2b-4614-8394-532460507e29
Jun  7 16:26:52.020: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c71d9029b7826fae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c71d9029b7826fae is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: bcd1ceb5-7821-4588-960a-4558925b2643
Jun  7 16:26:57.510: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c71d9029b7826fae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c71d9029b7826fae is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: e409e82c-773f-4485-9380-bcad6e83d38a
Jun  7 16:27:02.865: INFO: Successfully deleted PD "aws://us-east-1a/vol-0c71d9029b7826fae".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:27:02.865: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5305" for this suite.
... skipping 23 lines ...
Jun  7 16:26:13.474: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4175-e2e-sc984rl
STEP: creating a claim
Jun  7 16:26:13.506: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6pjb
STEP: Creating a pod to test exec-volume-test
Jun  7 16:26:13.618: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6pjb" in namespace "volume-4175" to be "Succeeded or Failed"
Jun  7 16:26:13.648: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.728174ms
Jun  7 16:26:15.680: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062776473s
Jun  7 16:26:17.712: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094791911s
Jun  7 16:26:19.745: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127151494s
Jun  7 16:26:21.777: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159370902s
Jun  7 16:26:23.810: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192340597s
Jun  7 16:26:25.842: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.224655776s
Jun  7 16:26:27.875: INFO: Pod "exec-volume-test-dynamicpv-6pjb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.257148264s
STEP: Saw pod success
Jun  7 16:26:27.875: INFO: Pod "exec-volume-test-dynamicpv-6pjb" satisfied condition "Succeeded or Failed"
Jun  7 16:26:27.906: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod exec-volume-test-dynamicpv-6pjb container exec-container-dynamicpv-6pjb: <nil>
STEP: delete the pod
Jun  7 16:26:27.977: INFO: Waiting for pod exec-volume-test-dynamicpv-6pjb to disappear
Jun  7 16:26:28.008: INFO: Pod exec-volume-test-dynamicpv-6pjb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6pjb
Jun  7 16:26:28.008: INFO: Deleting pod "exec-volume-test-dynamicpv-6pjb" in namespace "volume-4175"
... skipping 115 lines ...
Jun  7 16:24:19.205: INFO: Creating resource for dynamic PV
Jun  7 16:24:19.205: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5164-e2e-sctqvwk
STEP: creating a claim
Jun  7 16:24:19.238: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 16:24:19.347: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6sdm6" in namespace "snapshotting-5164" to be "Succeeded or Failed"
Jun  7 16:24:19.378: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.739346ms
Jun  7 16:24:21.410: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063109472s
Jun  7 16:24:23.441: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094283995s
Jun  7 16:24:25.473: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125939514s
Jun  7 16:24:27.504: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157163208s
Jun  7 16:24:29.538: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190992333s
... skipping 2 lines ...
Jun  7 16:24:35.640: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.293291457s
Jun  7 16:24:37.672: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.324661831s
Jun  7 16:24:39.707: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Pending", Reason="", readiness=false. Elapsed: 20.360063664s
Jun  7 16:24:41.739: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Running", Reason="", readiness=true. Elapsed: 22.392092155s
Jun  7 16:24:43.772: INFO: Pod "pvc-snapshottable-tester-6sdm6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.4245624s
STEP: Saw pod success
Jun  7 16:24:43.772: INFO: Pod "pvc-snapshottable-tester-6sdm6" satisfied condition "Succeeded or Failed"
Jun  7 16:24:43.835: INFO: Pod pvc-snapshottable-tester-6sdm6 has the following logs: 
Jun  7 16:24:43.835: INFO: Deleting pod "pvc-snapshottable-tester-6sdm6" in namespace "snapshotting-5164"
Jun  7 16:24:43.874: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6sdm6" to be fully deleted
Jun  7 16:24:43.905: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com94p9j] to have phase Bound
Jun  7 16:24:43.936: INFO: PersistentVolumeClaim ebs.csi.aws.com94p9j found and phase=Bound (30.833992ms)
STEP: [init] checking the claim
... skipping 54 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.lyccc3Uj6/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  7 16:25:37.504: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-7rm6b" in namespace "snapshotting-5164" to be "Succeeded or Failed"
Jun  7 16:25:37.534: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 30.611206ms
Jun  7 16:25:39.566: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061978719s
Jun  7 16:25:41.598: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094314703s
Jun  7 16:25:43.631: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126819582s
Jun  7 16:25:45.663: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159502808s
Jun  7 16:25:47.695: INFO: Pod "pvc-snapshottable-data-tester-7rm6b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.191033286s
STEP: Saw pod success
Jun  7 16:25:47.695: INFO: Pod "pvc-snapshottable-data-tester-7rm6b" satisfied condition "Succeeded or Failed"
Jun  7 16:25:47.759: INFO: Pod pvc-snapshottable-data-tester-7rm6b has the following logs: 
Jun  7 16:25:47.759: INFO: Deleting pod "pvc-snapshottable-data-tester-7rm6b" in namespace "snapshotting-5164"
Jun  7 16:25:47.809: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-7rm6b" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 16:26:09.967: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5164 exec restored-pvc-tester-lgxjb --namespace=snapshotting-5164 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun  7 16:26:35.360: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:36.392: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:37.426: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:38.458: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:39.490: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:40.523: INFO: volumesnapshotcontents pre-provisioned-snapcontent-604710b9-f1f0-480f-80f7-5614d9d35e88 has been found and is not deleted
Jun  7 16:26:41.523: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  7 16:26:41.556: INFO: Pod restored-pvc-tester-lgxjb has the following logs: 
Jun  7 16:26:41.556: INFO: Deleting pod "restored-pvc-tester-lgxjb" in namespace "snapshotting-5164"
Jun  7 16:26:41.631: INFO: Wait up to 5m0s for pod "restored-pvc-tester-lgxjb" to be fully deleted
Jun  7 16:27:17.693: INFO: deleting claim "snapshotting-5164"/"pvc-8v6zk"
... skipping 187 lines ...
Jun  7 16:24:31.459: INFO: Creating resource for dynamic PV
Jun  7 16:24:31.459: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5379-e2e-scx8q8x
STEP: creating a claim
Jun  7 16:24:31.491: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 16:24:31.590: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-5z5jt" in namespace "snapshotting-5379" to be "Succeeded or Failed"
Jun  7 16:24:31.621: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 30.228779ms
Jun  7 16:24:33.652: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061901598s
Jun  7 16:24:35.701: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110161716s
Jun  7 16:24:37.731: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140975266s
Jun  7 16:24:39.764: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173733003s
Jun  7 16:24:41.796: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.205640869s
... skipping 9 lines ...
Jun  7 16:25:02.111: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 30.520795814s
Jun  7 16:25:04.142: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 32.551759582s
Jun  7 16:25:06.173: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 34.582691409s
Jun  7 16:25:08.204: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Pending", Reason="", readiness=false. Elapsed: 36.61383508s
Jun  7 16:25:10.236: INFO: Pod "pvc-snapshottable-tester-5z5jt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.645410455s
STEP: Saw pod success
Jun  7 16:25:10.236: INFO: Pod "pvc-snapshottable-tester-5z5jt" satisfied condition "Succeeded or Failed"
Jun  7 16:25:10.299: INFO: Pod pvc-snapshottable-tester-5z5jt has the following logs: 
Jun  7 16:25:10.300: INFO: Deleting pod "pvc-snapshottable-tester-5z5jt" in namespace "snapshotting-5379"
Jun  7 16:25:10.340: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-5z5jt" to be fully deleted
Jun  7 16:25:10.370: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com9j59q] to have phase Bound
Jun  7 16:25:10.401: INFO: PersistentVolumeClaim ebs.csi.aws.com9j59q found and phase=Bound (30.49871ms)
STEP: [init] checking the claim
... skipping 56 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.lyccc3Uj6/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  7 16:26:07.984: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2kgcm" in namespace "snapshotting-5379" to be "Succeeded or Failed"
Jun  7 16:26:08.015: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.453474ms
Jun  7 16:26:10.046: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061454735s
Jun  7 16:26:12.077: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093120591s
Jun  7 16:26:14.109: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125363599s
Jun  7 16:26:16.141: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157353384s
Jun  7 16:26:18.173: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188654478s
Jun  7 16:26:20.205: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221360344s
Jun  7 16:26:22.237: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.252736676s
Jun  7 16:26:24.268: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.283452532s
Jun  7 16:26:26.300: INFO: Pod "pvc-snapshottable-data-tester-2kgcm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.316253958s
STEP: Saw pod success
Jun  7 16:26:26.300: INFO: Pod "pvc-snapshottable-data-tester-2kgcm" satisfied condition "Succeeded or Failed"
Jun  7 16:26:26.373: INFO: Pod pvc-snapshottable-data-tester-2kgcm has the following logs: 
Jun  7 16:26:26.373: INFO: Deleting pod "pvc-snapshottable-data-tester-2kgcm" in namespace "snapshotting-5379"
Jun  7 16:26:26.419: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2kgcm" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 16:26:40.596: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5379 exec restored-pvc-tester-2qvfb --namespace=snapshotting-5379 -- cat /mnt/test/data'
... skipping 231 lines ...

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 55 lines ...
Jun  7 16:27:03.087: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1950-e2e-scx8s9r
STEP: creating a claim
Jun  7 16:27:03.120: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4gsk
STEP: Creating a pod to test subpath
Jun  7 16:27:03.215: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4gsk" in namespace "provisioning-1950" to be "Succeeded or Failed"
Jun  7 16:27:03.246: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.864096ms
Jun  7 16:27:05.278: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062205997s
Jun  7 16:27:07.312: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09701545s
Jun  7 16:27:09.344: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128621825s
Jun  7 16:27:11.377: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161256938s
Jun  7 16:27:13.408: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192891808s
... skipping 10 lines ...
Jun  7 16:27:35.770: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 32.554395494s
Jun  7 16:27:37.802: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 34.586381112s
Jun  7 16:27:39.834: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 36.618233587s
Jun  7 16:27:41.867: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Pending", Reason="", readiness=false. Elapsed: 38.651264383s
Jun  7 16:27:43.901: INFO: Pod "pod-subpath-test-dynamicpv-4gsk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.685651651s
STEP: Saw pod success
Jun  7 16:27:43.901: INFO: Pod "pod-subpath-test-dynamicpv-4gsk" satisfied condition "Succeeded or Failed"
Jun  7 16:27:43.932: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod pod-subpath-test-dynamicpv-4gsk container test-container-subpath-dynamicpv-4gsk: <nil>
STEP: delete the pod
Jun  7 16:27:44.005: INFO: Waiting for pod pod-subpath-test-dynamicpv-4gsk to disappear
Jun  7 16:27:44.038: INFO: Pod pod-subpath-test-dynamicpv-4gsk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4gsk
Jun  7 16:27:44.038: INFO: Deleting pod "pod-subpath-test-dynamicpv-4gsk" in namespace "provisioning-1950"
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:27:01.654: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:27:01.822: INFO: Creating resource for dynamic PV
Jun  7 16:27:01.822: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5418-e2e-sc2tzz4
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:27:08.056: INFO: Deleting pod "pod-92ff2efa-5aaa-4915-aa54-4a9cc3fe92e4" in namespace "volumemode-5418"
Jun  7 16:27:08.089: INFO: Wait up to 5m0s for pod "pod-92ff2efa-5aaa-4915-aa54-4a9cc3fe92e4" to be fully deleted
STEP: Deleting pvc
Jun  7 16:27:14.228: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comshgz8"
Jun  7 16:27:14.260: INFO: Waiting up to 5m0s for PersistentVolume pvc-4fd20400-e2c2-42ed-bf22-6ef8768c0c49 to get deleted
Jun  7 16:27:14.291: INFO: PersistentVolume pvc-4fd20400-e2c2-42ed-bf22-6ef8768c0c49 found and phase=Released (30.090546ms)
... skipping 16 lines ...

• [SLOW TEST:63.054 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  7 16:27:03.655: INFO: Creating resource for dynamic PV
Jun  7 16:27:03.655: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9004jk4kv
STEP: creating a claim
Jun  7 16:27:03.688: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9004
Jun  7 16:27:03.791: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9004" in namespace "provisioning-9004" to be "Succeeded or Failed"
Jun  7 16:27:03.823: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 32.077198ms
Jun  7 16:27:05.856: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064958738s
Jun  7 16:27:07.889: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097381026s
Jun  7 16:27:09.921: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129833282s
Jun  7 16:27:11.953: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162076757s
Jun  7 16:27:13.985: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193357471s
Jun  7 16:27:16.016: INFO: Pod "volume-prep-provisioning-9004": Phase="Pending", Reason="", readiness=false. Elapsed: 12.225067573s
Jun  7 16:27:18.048: INFO: Pod "volume-prep-provisioning-9004": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.256398341s
STEP: Saw pod success
Jun  7 16:27:18.048: INFO: Pod "volume-prep-provisioning-9004" satisfied condition "Succeeded or Failed"
Jun  7 16:27:18.048: INFO: Deleting pod "volume-prep-provisioning-9004" in namespace "provisioning-9004"
Jun  7 16:27:18.085: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9004" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-rnfk
STEP: Checking for subpath error in container status
Jun  7 16:27:52.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-rnfk" in namespace "provisioning-9004"
Jun  7 16:27:52.254: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rnfk" to be fully deleted
STEP: Deleting pod
Jun  7 16:27:52.285: INFO: Deleting pod "pod-subpath-test-dynamicpv-rnfk" in namespace "provisioning-9004"
STEP: Deleting pvc
Jun  7 16:27:52.382: INFO: Deleting PersistentVolumeClaim "awsxhjqn"
... skipping 28 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 123 lines ...
Jun  7 16:27:34.990: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2436p9vjs
STEP: creating a claim
Jun  7 16:27:35.021: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-kbk2
STEP: Creating a pod to test exec-volume-test
Jun  7 16:27:35.119: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-kbk2" in namespace "volume-2436" to be "Succeeded or Failed"
Jun  7 16:27:35.150: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.464556ms
Jun  7 16:27:37.181: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061335279s
Jun  7 16:27:39.212: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093205918s
Jun  7 16:27:41.245: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125398612s
Jun  7 16:27:43.276: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157189732s
Jun  7 16:27:45.309: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18999977s
... skipping 2 lines ...
Jun  7 16:27:51.461: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.341920533s
Jun  7 16:27:53.493: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.374168052s
Jun  7 16:27:55.526: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.406775591s
Jun  7 16:27:57.560: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.440512321s
Jun  7 16:27:59.592: INFO: Pod "exec-volume-test-dynamicpv-kbk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.4724512s
STEP: Saw pod success
Jun  7 16:27:59.592: INFO: Pod "exec-volume-test-dynamicpv-kbk2" satisfied condition "Succeeded or Failed"
Jun  7 16:27:59.623: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod exec-volume-test-dynamicpv-kbk2 container exec-container-dynamicpv-kbk2: <nil>
STEP: delete the pod
Jun  7 16:27:59.692: INFO: Waiting for pod exec-volume-test-dynamicpv-kbk2 to disappear
Jun  7 16:27:59.723: INFO: Pod exec-volume-test-dynamicpv-kbk2 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-kbk2
Jun  7 16:27:59.723: INFO: Deleting pod "exec-volume-test-dynamicpv-kbk2" in namespace "volume-2436"
... skipping 54 lines ...
Jun  7 16:27:40.931: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8193ppgrw
STEP: creating a claim
Jun  7 16:27:40.963: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  7 16:27:41.026: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 16:27:41.089: INFO: Error updating pvc awsqpm5v: PersistentVolumeClaim "awsqpm5v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8193ppgrw",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  7 16:28:11.231: INFO: Error updating pvc awsqpm5v: PersistentVolumeClaim "awsqpm5v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 32 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:27:34.343: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  7 16:27:34.501: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:27:34.501: INFO: Creating resource for dynamic PV
Jun  7 16:27:34.501: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2266z7zx7
STEP: creating a claim
Jun  7 16:27:34.533: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vvww
STEP: Checking for subpath error in container status
Jun  7 16:27:58.700: INFO: Deleting pod "pod-subpath-test-dynamicpv-vvww" in namespace "provisioning-2266"
Jun  7 16:27:58.735: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vvww" to be fully deleted
STEP: Deleting pod
Jun  7 16:28:08.801: INFO: Deleting pod "pod-subpath-test-dynamicpv-vvww" in namespace "provisioning-2266"
STEP: Deleting pvc
Jun  7 16:28:08.904: INFO: Deleting PersistentVolumeClaim "awsctxdj"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 131 lines ...
Jun  7 16:28:06.985: INFO: Waiting for pod aws-client to disappear
Jun  7 16:28:07.017: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 16:28:07.017: INFO: Deleting PersistentVolumeClaim "pvc-fr9nz"
Jun  7 16:28:07.051: INFO: Deleting PersistentVolume "aws-xpj4j"
Jun  7 16:28:07.275: INFO: Couldn't delete PD "aws://us-east-1a/vol-056e7d8b8be945ff8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-056e7d8b8be945ff8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 10846d59-a7bc-4171-aa4f-777a03f0b316
Jun  7 16:28:12.616: INFO: Couldn't delete PD "aws://us-east-1a/vol-056e7d8b8be945ff8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-056e7d8b8be945ff8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 5268006f-c81c-49d3-b7b6-bea2d494c2cc
Jun  7 16:28:18.113: INFO: Couldn't delete PD "aws://us-east-1a/vol-056e7d8b8be945ff8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-056e7d8b8be945ff8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: c7eb8609-d55a-4d46-8fb5-35773589f3b5
Jun  7 16:28:23.752: INFO: Couldn't delete PD "aws://us-east-1a/vol-056e7d8b8be945ff8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-056e7d8b8be945ff8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 048a3d49-7d23-488f-aa8b-d5e18d07445f
Jun  7 16:28:29.330: INFO: Successfully deleted PD "aws://us-east-1a/vol-056e7d8b8be945ff8".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:28:29.330: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2962" for this suite.
... skipping 127 lines ...
Jun  7 16:28:04.863: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 16:28:05.188: INFO: Successfully created a new PD: "aws://us-east-1a/vol-01ae204b29a1ac5de".
Jun  7 16:28:05.188: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-4n94
STEP: Creating a pod to test exec-volume-test
Jun  7 16:28:05.221: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-4n94" in namespace "volume-3192" to be "Succeeded or Failed"
Jun  7 16:28:05.251: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Pending", Reason="", readiness=false. Elapsed: 30.031295ms
Jun  7 16:28:07.282: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061040779s
Jun  7 16:28:09.334: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Pending", Reason="", readiness=false. Elapsed: 4.112926383s
Jun  7 16:28:11.366: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Pending", Reason="", readiness=false. Elapsed: 6.145451803s
Jun  7 16:28:13.397: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Pending", Reason="", readiness=false. Elapsed: 8.17632184s
Jun  7 16:28:15.430: INFO: Pod "exec-volume-test-inlinevolume-4n94": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.209456385s
STEP: Saw pod success
Jun  7 16:28:15.430: INFO: Pod "exec-volume-test-inlinevolume-4n94" satisfied condition "Succeeded or Failed"
Jun  7 16:28:15.460: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod exec-volume-test-inlinevolume-4n94 container exec-container-inlinevolume-4n94: <nil>
STEP: delete the pod
Jun  7 16:28:15.533: INFO: Waiting for pod exec-volume-test-inlinevolume-4n94 to disappear
Jun  7 16:28:15.564: INFO: Pod exec-volume-test-inlinevolume-4n94 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-4n94
Jun  7 16:28:15.564: INFO: Deleting pod "exec-volume-test-inlinevolume-4n94" in namespace "volume-3192"
Jun  7 16:28:15.767: INFO: Couldn't delete PD "aws://us-east-1a/vol-01ae204b29a1ac5de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ae204b29a1ac5de is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: ae780dfc-90c1-4216-9f7a-560b8034fb65
Jun  7 16:28:21.167: INFO: Couldn't delete PD "aws://us-east-1a/vol-01ae204b29a1ac5de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ae204b29a1ac5de is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: de5e0e70-563d-494a-b044-48067b629f5a
Jun  7 16:28:26.566: INFO: Couldn't delete PD "aws://us-east-1a/vol-01ae204b29a1ac5de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ae204b29a1ac5de is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: dc43f978-e610-45d1-b5a5-c5150d39e1b2
Jun  7 16:28:31.906: INFO: Successfully deleted PD "aws://us-east-1a/vol-01ae204b29a1ac5de".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:28:31.906: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3192" for this suite.
... skipping 104 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 86 lines ...
Jun  7 16:27:44.862: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-555-e2e-scfh84h
STEP: creating a claim
Jun  7 16:27:44.895: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jwlv
STEP: Creating a pod to test multi_subpath
Jun  7 16:27:44.990: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jwlv" in namespace "provisioning-555" to be "Succeeded or Failed"
Jun  7 16:27:45.022: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.142815ms
Jun  7 16:27:47.053: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062304185s
Jun  7 16:27:49.084: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093470779s
Jun  7 16:27:51.116: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12516383s
Jun  7 16:27:53.148: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157856191s
Jun  7 16:27:55.180: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189059627s
Jun  7 16:27:57.211: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22044165s
Jun  7 16:27:59.244: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.253864155s
Jun  7 16:28:01.276: INFO: Pod "pod-subpath-test-dynamicpv-jwlv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.285279136s
STEP: Saw pod success
Jun  7 16:28:01.276: INFO: Pod "pod-subpath-test-dynamicpv-jwlv" satisfied condition "Succeeded or Failed"
Jun  7 16:28:01.307: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-jwlv container test-container-subpath-dynamicpv-jwlv: <nil>
STEP: delete the pod
Jun  7 16:28:01.379: INFO: Waiting for pod pod-subpath-test-dynamicpv-jwlv to disappear
Jun  7 16:28:01.410: INFO: Pod pod-subpath-test-dynamicpv-jwlv no longer exists
STEP: Deleting pod
Jun  7 16:28:01.410: INFO: Deleting pod "pod-subpath-test-dynamicpv-jwlv" in namespace "provisioning-555"
... skipping 66 lines ...
STEP: Deleting pod hostexec-ip-172-20-56-140.ec2.internal-rg8m5 in namespace volumemode-3039
Jun  7 16:28:15.916: INFO: Deleting pod "pod-7b140cba-6996-436c-b00a-628f6c7badab" in namespace "volumemode-3039"
Jun  7 16:28:15.947: INFO: Wait up to 5m0s for pod "pod-7b140cba-6996-436c-b00a-628f6c7badab" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 16:28:26.013: INFO: Deleting PersistentVolumeClaim "pvc-24clb"
Jun  7 16:28:26.044: INFO: Deleting PersistentVolume "aws-6qx2c"
Jun  7 16:28:26.246: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f2fdb7c9c325a579", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f2fdb7c9c325a579 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 3b30b0a5-e28d-480b-98e4-bbe41e1fe9c6
Jun  7 16:28:31.605: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f2fdb7c9c325a579", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f2fdb7c9c325a579 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: f7807fe0-efdf-4e26-832d-11bb78eb04e4
Jun  7 16:28:37.001: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f2fdb7c9c325a579", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f2fdb7c9c325a579 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 00957a87-c551-4bc6-b786-36abe2f34e41
Jun  7 16:28:42.400: INFO: Successfully deleted PD "aws://us-east-1a/vol-0f2fdb7c9c325a579".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:28:42.400: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3039" for this suite.
... skipping 239 lines ...
Jun  7 16:28:04.339: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6544dhmvl
STEP: creating a claim
Jun  7 16:28:04.370: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5b6f
STEP: Creating a pod to test subpath
Jun  7 16:28:04.466: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5b6f" in namespace "provisioning-6544" to be "Succeeded or Failed"
Jun  7 16:28:04.497: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 31.22182ms
Jun  7 16:28:06.528: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062324903s
Jun  7 16:28:08.559: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093299369s
Jun  7 16:28:10.590: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124240221s
Jun  7 16:28:12.621: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155248397s
Jun  7 16:28:14.653: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187029417s
... skipping 2 lines ...
Jun  7 16:28:20.747: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 16.280572034s
Jun  7 16:28:22.778: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 18.312312629s
Jun  7 16:28:24.810: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 20.343826362s
Jun  7 16:28:26.842: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Pending", Reason="", readiness=false. Elapsed: 22.375406772s
Jun  7 16:28:28.873: INFO: Pod "pod-subpath-test-dynamicpv-5b6f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.407194016s
STEP: Saw pod success
Jun  7 16:28:28.873: INFO: Pod "pod-subpath-test-dynamicpv-5b6f" satisfied condition "Succeeded or Failed"
Jun  7 16:28:28.905: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-5b6f container test-container-volume-dynamicpv-5b6f: <nil>
STEP: delete the pod
Jun  7 16:28:28.979: INFO: Waiting for pod pod-subpath-test-dynamicpv-5b6f to disappear
Jun  7 16:28:29.014: INFO: Pod pod-subpath-test-dynamicpv-5b6f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5b6f
Jun  7 16:28:29.014: INFO: Deleting pod "pod-subpath-test-dynamicpv-5b6f" in namespace "provisioning-6544"
... skipping 96 lines ...
Jun  7 16:28:24.578: INFO: PersistentVolumeClaim pvc-l5h5k found but phase is Pending instead of Bound.
Jun  7 16:28:26.609: INFO: PersistentVolumeClaim pvc-l5h5k found and phase=Bound (16.28864911s)
Jun  7 16:28:26.609: INFO: Waiting up to 3m0s for PersistentVolume aws-vwvwv to have phase Bound
Jun  7 16:28:26.640: INFO: PersistentVolume aws-vwvwv found and phase=Bound (30.988804ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-cr4q
STEP: Creating a pod to test exec-volume-test
Jun  7 16:28:26.733: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-cr4q" in namespace "volume-1355" to be "Succeeded or Failed"
Jun  7 16:28:26.764: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 30.738678ms
Jun  7 16:28:28.795: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061868058s
Jun  7 16:28:30.826: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092705676s
Jun  7 16:28:32.857: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1243377s
Jun  7 16:28:34.889: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15636804s
Jun  7 16:28:36.921: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187811457s
Jun  7 16:28:38.956: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223431264s
Jun  7 16:28:40.988: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.254951937s
STEP: Saw pod success
Jun  7 16:28:40.988: INFO: Pod "exec-volume-test-preprovisionedpv-cr4q" satisfied condition "Succeeded or Failed"
Jun  7 16:28:41.019: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod exec-volume-test-preprovisionedpv-cr4q container exec-container-preprovisionedpv-cr4q: <nil>
STEP: delete the pod
Jun  7 16:28:41.093: INFO: Waiting for pod exec-volume-test-preprovisionedpv-cr4q to disappear
Jun  7 16:28:41.124: INFO: Pod exec-volume-test-preprovisionedpv-cr4q no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-cr4q
Jun  7 16:28:41.124: INFO: Deleting pod "exec-volume-test-preprovisionedpv-cr4q" in namespace "volume-1355"
STEP: Deleting pv and pvc
Jun  7 16:28:41.154: INFO: Deleting PersistentVolumeClaim "pvc-l5h5k"
Jun  7 16:28:41.191: INFO: Deleting PersistentVolume "aws-vwvwv"
Jun  7 16:28:41.467: INFO: Couldn't delete PD "aws://us-east-1a/vol-0cdb5f79911dbd184", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cdb5f79911dbd184 is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: ddfa935a-3077-4554-b19c-34097838cc03
Jun  7 16:28:46.782: INFO: Couldn't delete PD "aws://us-east-1a/vol-0cdb5f79911dbd184", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cdb5f79911dbd184 is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: 0d46b3e0-0199-434e-974a-f54447655281
Jun  7 16:28:52.142: INFO: Successfully deleted PD "aws://us-east-1a/vol-0cdb5f79911dbd184".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:28:52.142: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1355" for this suite.
... skipping 293 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 31 lines ...
Jun  7 16:28:29.561: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 16:28:29.906: INFO: Successfully created a new PD: "aws://us-east-1a/vol-02599ecdbf7f6c4e8".
Jun  7 16:28:29.906: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-m5xh
STEP: Creating a pod to test exec-volume-test
Jun  7 16:28:29.951: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-m5xh" in namespace "volume-5826" to be "Succeeded or Failed"
Jun  7 16:28:29.983: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 31.876577ms
Jun  7 16:28:32.027: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.076115725s
Jun  7 16:28:34.059: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108124931s
Jun  7 16:28:36.091: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140011092s
Jun  7 16:28:38.123: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171997648s
Jun  7 16:28:40.155: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204749536s
Jun  7 16:28:42.187: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.236343133s
Jun  7 16:28:44.219: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.268066146s
Jun  7 16:28:46.253: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.302305817s
Jun  7 16:28:48.286: INFO: Pod "exec-volume-test-inlinevolume-m5xh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.335739686s
STEP: Saw pod success
Jun  7 16:28:48.287: INFO: Pod "exec-volume-test-inlinevolume-m5xh" satisfied condition "Succeeded or Failed"
Jun  7 16:28:48.318: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod exec-volume-test-inlinevolume-m5xh container exec-container-inlinevolume-m5xh: <nil>
STEP: delete the pod
Jun  7 16:28:48.439: INFO: Waiting for pod exec-volume-test-inlinevolume-m5xh to disappear
Jun  7 16:28:48.471: INFO: Pod exec-volume-test-inlinevolume-m5xh no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-m5xh
Jun  7 16:28:48.471: INFO: Deleting pod "exec-volume-test-inlinevolume-m5xh" in namespace "volume-5826"
Jun  7 16:28:48.684: INFO: Couldn't delete PD "aws://us-east-1a/vol-02599ecdbf7f6c4e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02599ecdbf7f6c4e8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: 6f4926ef-af60-4713-927f-dddbccf1395b
Jun  7 16:28:54.012: INFO: Couldn't delete PD "aws://us-east-1a/vol-02599ecdbf7f6c4e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02599ecdbf7f6c4e8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: a6027be6-aea0-4908-8c99-17c54903e7a5
Jun  7 16:28:59.437: INFO: Couldn't delete PD "aws://us-east-1a/vol-02599ecdbf7f6c4e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02599ecdbf7f6c4e8 is currently attached to i-04d4fb706bad8d38d
	status code: 400, request id: b8d97e57-7ee4-4b37-9725-bb72664981c0
Jun  7 16:29:04.839: INFO: Successfully deleted PD "aws://us-east-1a/vol-02599ecdbf7f6c4e8".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:29:04.839: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5826" for this suite.
... skipping 33 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:28:34.615: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:28:34.784: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 16:28:35.276: INFO: Successfully created a new PD: "aws://us-east-1a/vol-0e008b4e43814f2fb".
Jun  7 16:28:35.276: INFO: Creating resource for pre-provisioned PV
Jun  7 16:28:35.276: INFO: Creating PVC and PV
... skipping 4 lines ...
Jun  7 16:28:37.489: INFO: PersistentVolumeClaim pvc-wk59c found but phase is Pending instead of Bound.
Jun  7 16:28:39.519: INFO: PersistentVolumeClaim pvc-wk59c found but phase is Pending instead of Bound.
Jun  7 16:28:41.551: INFO: PersistentVolumeClaim pvc-wk59c found and phase=Bound (6.129032147s)
Jun  7 16:28:41.551: INFO: Waiting up to 3m0s for PersistentVolume aws-5wqxz to have phase Bound
Jun  7 16:28:41.581: INFO: PersistentVolume aws-5wqxz found and phase=Bound (30.355125ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:28:43.771: INFO: Deleting pod "pod-45006e33-72d0-4f77-b10a-0db21ac02fb4" in namespace "volumemode-4004"
Jun  7 16:28:43.805: INFO: Wait up to 5m0s for pod "pod-45006e33-72d0-4f77-b10a-0db21ac02fb4" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 16:28:51.867: INFO: Deleting PersistentVolumeClaim "pvc-wk59c"
Jun  7 16:28:51.900: INFO: Deleting PersistentVolume "aws-5wqxz"
Jun  7 16:28:52.094: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e008b4e43814f2fb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e008b4e43814f2fb is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: 7e03b48c-864f-47de-89fe-9ae0b6bcc493
Jun  7 16:28:57.434: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e008b4e43814f2fb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e008b4e43814f2fb is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: d79a2c1a-1f19-44c4-bbec-d4a4b8473f7e
Jun  7 16:29:02.740: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e008b4e43814f2fb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e008b4e43814f2fb is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: 34e04bf1-ee7c-4b3d-8726-cbbde28cffb2
Jun  7 16:29:08.091: INFO: Successfully deleted PD "aws://us-east-1a/vol-0e008b4e43814f2fb".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:29:08.091: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4004" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 415 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:28:29.634: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  7 16:28:29.791: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:28:29.791: INFO: Creating resource for dynamic PV
Jun  7 16:28:29.791: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-40609b8fw
STEP: creating a claim
Jun  7 16:28:29.823: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dt8c
STEP: Checking for subpath error in container status
Jun  7 16:28:53.982: INFO: Deleting pod "pod-subpath-test-dynamicpv-dt8c" in namespace "provisioning-4060"
Jun  7 16:28:54.013: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dt8c" to be fully deleted
STEP: Deleting pod
Jun  7 16:29:06.078: INFO: Deleting pod "pod-subpath-test-dynamicpv-dt8c" in namespace "provisioning-4060"
STEP: Deleting pvc
Jun  7 16:29:06.169: INFO: Deleting PersistentVolumeClaim "awsgwgpm"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 16:29:26.467: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 82 lines ...
Jun  7 16:29:04.651: INFO: Pod aws-client still exists
Jun  7 16:29:06.621: INFO: Waiting for pod aws-client to disappear
Jun  7 16:29:06.655: INFO: Pod aws-client still exists
Jun  7 16:29:08.619: INFO: Waiting for pod aws-client to disappear
Jun  7 16:29:08.651: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  7 16:29:09.018: INFO: Couldn't delete PD "aws://us-east-1a/vol-0183c664058a982a1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0183c664058a982a1 is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: ec5e289b-508c-4f5b-8fcc-659f8d251bde
Jun  7 16:29:14.418: INFO: Couldn't delete PD "aws://us-east-1a/vol-0183c664058a982a1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0183c664058a982a1 is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: b1d1f1bd-5cf9-4e0a-969d-7e452dbcb92a
Jun  7 16:29:19.730: INFO: Couldn't delete PD "aws://us-east-1a/vol-0183c664058a982a1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0183c664058a982a1 is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: 2134ec4b-720e-4a99-88d3-ab7b5bb3cf9f
Jun  7 16:29:25.095: INFO: Couldn't delete PD "aws://us-east-1a/vol-0183c664058a982a1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0183c664058a982a1 is currently attached to i-0f5255f3084a895d8
	status code: 400, request id: 2a83ca63-ca1a-4a1b-9dec-020c3d385efb
Jun  7 16:29:30.463: INFO: Successfully deleted PD "aws://us-east-1a/vol-0183c664058a982a1".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:29:30.463: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8589" for this suite.
... skipping 24 lines ...
Jun  7 16:28:37.046: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-64538b6tx
STEP: creating a claim
Jun  7 16:28:37.077: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ngx7
STEP: Creating a pod to test exec-volume-test
Jun  7 16:28:37.177: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ngx7" in namespace "volume-6453" to be "Succeeded or Failed"
Jun  7 16:28:37.210: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.395028ms
Jun  7 16:28:39.241: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063474809s
Jun  7 16:28:41.274: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096598048s
Jun  7 16:28:43.306: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128707953s
Jun  7 16:28:45.337: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159858769s
Jun  7 16:28:47.368: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190864102s
Jun  7 16:28:49.401: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.222963907s
Jun  7 16:28:51.431: INFO: Pod "exec-volume-test-dynamicpv-ngx7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.253809168s
STEP: Saw pod success
Jun  7 16:28:51.431: INFO: Pod "exec-volume-test-dynamicpv-ngx7" satisfied condition "Succeeded or Failed"
Jun  7 16:28:51.462: INFO: Trying to get logs from node ip-172-20-36-23.ec2.internal pod exec-volume-test-dynamicpv-ngx7 container exec-container-dynamicpv-ngx7: <nil>
STEP: delete the pod
Jun  7 16:28:51.535: INFO: Waiting for pod exec-volume-test-dynamicpv-ngx7 to disappear
Jun  7 16:28:51.566: INFO: Pod exec-volume-test-dynamicpv-ngx7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ngx7
Jun  7 16:28:51.566: INFO: Deleting pod "exec-volume-test-dynamicpv-ngx7" in namespace "volume-6453"
... skipping 161 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:28:42.914: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:28:43.066: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:28:43.066: INFO: Creating resource for dynamic PV
Jun  7 16:28:43.066: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2774jh49p
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:28:47.284: INFO: Deleting pod "pod-230f426f-0616-448d-a55f-ff9a99bf181c" in namespace "volumemode-2774"
Jun  7 16:28:47.319: INFO: Wait up to 5m0s for pod "pod-230f426f-0616-448d-a55f-ff9a99bf181c" to be fully deleted
STEP: Deleting pvc
Jun  7 16:28:59.440: INFO: Deleting PersistentVolumeClaim "awsdbtnm"
Jun  7 16:28:59.472: INFO: Waiting up to 5m0s for PersistentVolume pvc-c3b16b7c-355f-4b59-9ffa-aba21be6b27c to get deleted
Jun  7 16:28:59.504: INFO: PersistentVolume pvc-c3b16b7c-355f-4b59-9ffa-aba21be6b27c found and phase=Released (32.199665ms)
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 16:29:39.859: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 184 lines ...
Jun  7 16:27:46.965: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8062rjcb4      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-8062    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-8062rjcb4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8062    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-8062rjcb4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8062    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-8062rjcb4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8062rjcb4    f99c7cda-bbe6-4059-81f3-8f2452559efb 10715 0 2021-06-07 16:27:47 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-07 16:27:47 +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-pz5sg pvc- provisioning-8062  c8707add-3887-4a56-bcbc-a0077c719c2a 10716 0 2021-06-07 16:27:47 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-07 16:27:47 +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-8062rjcb4,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-c2d140f8-b331-4f0d-98c7-e3caef6a6b93 in namespace provisioning-8062
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  7 16:28:05.319: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-rcjk4" in namespace "provisioning-8062" to be "Succeeded or Failed"
Jun  7 16:28:05.349: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.695527ms
Jun  7 16:28:07.383: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064400399s
Jun  7 16:28:09.433: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114740147s
Jun  7 16:28:11.465: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.146656648s
Jun  7 16:28:13.496: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.177838345s
Jun  7 16:28:15.533: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.214210629s
... skipping 7 lines ...
Jun  7 16:28:31.790: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 26.47150615s
Jun  7 16:28:33.822: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 28.502917305s
Jun  7 16:28:35.853: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.533876088s
Jun  7 16:28:37.885: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.566130785s
Jun  7 16:28:39.917: INFO: Pod "pvc-volume-tester-writer-rcjk4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.598484126s
STEP: Saw pod success
Jun  7 16:28:39.917: INFO: Pod "pvc-volume-tester-writer-rcjk4" satisfied condition "Succeeded or Failed"
Jun  7 16:28:39.990: INFO: Pod pvc-volume-tester-writer-rcjk4 has the following logs: 
Jun  7 16:28:39.990: INFO: Deleting pod "pvc-volume-tester-writer-rcjk4" in namespace "provisioning-8062"
Jun  7 16:28:40.030: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-rcjk4" 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-36-23.ec2.internal"
Jun  7 16:28:40.158: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-jvj6n" in namespace "provisioning-8062" to be "Succeeded or Failed"
Jun  7 16:28:40.189: INFO: Pod "pvc-volume-tester-reader-jvj6n": Phase="Pending", Reason="", readiness=false. Elapsed: 30.715521ms
Jun  7 16:28:42.220: INFO: Pod "pvc-volume-tester-reader-jvj6n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.061558615s
STEP: Saw pod success
Jun  7 16:28:42.220: INFO: Pod "pvc-volume-tester-reader-jvj6n" satisfied condition "Succeeded or Failed"
Jun  7 16:28:42.285: INFO: Pod pvc-volume-tester-reader-jvj6n has the following logs: hello world

Jun  7 16:28:42.285: INFO: Deleting pod "pvc-volume-tester-reader-jvj6n" in namespace "provisioning-8062"
Jun  7 16:28:42.322: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-jvj6n" to be fully deleted
Jun  7 16:28:42.353: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-pz5sg] to have phase Bound
Jun  7 16:28:42.385: INFO: PersistentVolumeClaim pvc-pz5sg found and phase=Bound (31.437962ms)
... skipping 391 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:03.808: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  7 16:30:03.995: INFO: found topology map[topology.kubernetes.io/zone:us-east-1a]
Jun  7 16:30:03.995: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:30:03.995: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 136 lines ...
Jun  7 16:29:08.318: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7269-e2e-sc4w4vn
STEP: creating a claim
Jun  7 16:29:08.349: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ptkd
STEP: Creating a pod to test subpath
Jun  7 16:29:08.453: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ptkd" in namespace "provisioning-7269" to be "Succeeded or Failed"
Jun  7 16:29:08.484: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.245383ms
Jun  7 16:29:10.517: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063284142s
Jun  7 16:29:12.552: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098127142s
Jun  7 16:29:14.585: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.132044736s
Jun  7 16:29:16.618: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.164202663s
Jun  7 16:29:18.651: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.197990002s
... skipping 2 lines ...
Jun  7 16:29:24.750: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.296644353s
Jun  7 16:29:26.781: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.32758916s
Jun  7 16:29:28.813: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 20.360061345s
Jun  7 16:29:30.844: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 22.390747645s
Jun  7 16:29:32.875: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.421889225s
STEP: Saw pod success
Jun  7 16:29:32.875: INFO: Pod "pod-subpath-test-dynamicpv-ptkd" satisfied condition "Succeeded or Failed"
Jun  7 16:29:32.910: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-ptkd container test-container-subpath-dynamicpv-ptkd: <nil>
STEP: delete the pod
Jun  7 16:29:32.984: INFO: Waiting for pod pod-subpath-test-dynamicpv-ptkd to disappear
Jun  7 16:29:33.014: INFO: Pod pod-subpath-test-dynamicpv-ptkd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ptkd
Jun  7 16:29:33.014: INFO: Deleting pod "pod-subpath-test-dynamicpv-ptkd" in namespace "provisioning-7269"
STEP: Creating pod pod-subpath-test-dynamicpv-ptkd
STEP: Creating a pod to test subpath
Jun  7 16:29:33.084: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ptkd" in namespace "provisioning-7269" to be "Succeeded or Failed"
Jun  7 16:29:33.115: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.247618ms
Jun  7 16:29:35.146: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061316596s
Jun  7 16:29:37.177: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092245839s
Jun  7 16:29:39.208: INFO: Pod "pod-subpath-test-dynamicpv-ptkd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.12348061s
STEP: Saw pod success
Jun  7 16:29:39.208: INFO: Pod "pod-subpath-test-dynamicpv-ptkd" satisfied condition "Succeeded or Failed"
Jun  7 16:29:39.239: INFO: Trying to get logs from node ip-172-20-56-140.ec2.internal pod pod-subpath-test-dynamicpv-ptkd container test-container-subpath-dynamicpv-ptkd: <nil>
STEP: delete the pod
Jun  7 16:29:39.313: INFO: Waiting for pod pod-subpath-test-dynamicpv-ptkd to disappear
Jun  7 16:29:39.344: INFO: Pod pod-subpath-test-dynamicpv-ptkd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ptkd
Jun  7 16:29:39.344: INFO: Deleting pod "pod-subpath-test-dynamicpv-ptkd" in namespace "provisioning-7269"
... skipping 371 lines ...
Jun  7 16:29:03.963: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3530-e2e-scstxtp
STEP: creating a claim
Jun  7 16:29:03.997: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5694
STEP: Creating a pod to test subpath
Jun  7 16:29:04.099: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5694" in namespace "provisioning-3530" to be "Succeeded or Failed"
Jun  7 16:29:04.131: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 31.651562ms
Jun  7 16:29:06.162: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062782351s
Jun  7 16:29:08.193: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094271035s
Jun  7 16:29:10.224: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125399363s
Jun  7 16:29:12.257: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157750095s
Jun  7 16:29:14.288: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189113146s
... skipping 10 lines ...
Jun  7 16:29:36.648: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 32.549148702s
Jun  7 16:29:38.679: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 34.580449363s
Jun  7 16:29:40.712: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 36.612810162s
Jun  7 16:29:42.743: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Pending", Reason="", readiness=false. Elapsed: 38.644375947s
Jun  7 16:29:44.781: INFO: Pod "pod-subpath-test-dynamicpv-5694": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.681786606s
STEP: Saw pod success
Jun  7 16:29:44.781: INFO: Pod "pod-subpath-test-dynamicpv-5694" satisfied condition "Succeeded or Failed"
Jun  7 16:29:44.812: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod pod-subpath-test-dynamicpv-5694 container test-container-subpath-dynamicpv-5694: <nil>
STEP: delete the pod
Jun  7 16:29:44.913: INFO: Waiting for pod pod-subpath-test-dynamicpv-5694 to disappear
Jun  7 16:29:44.944: INFO: Pod pod-subpath-test-dynamicpv-5694 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5694
Jun  7 16:29:44.944: INFO: Deleting pod "pod-subpath-test-dynamicpv-5694" in namespace "provisioning-3530"
... skipping 109 lines ...
Jun  7 16:29:23.966: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-46318x8nk
STEP: creating a claim
Jun  7 16:29:23.997: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kx9z
STEP: Creating a pod to test subpath
Jun  7 16:29:24.097: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kx9z" in namespace "provisioning-4631" to be "Succeeded or Failed"
Jun  7 16:29:24.127: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 30.579975ms
Jun  7 16:29:26.159: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062165466s
Jun  7 16:29:28.192: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095348591s
Jun  7 16:29:30.223: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126113346s
Jun  7 16:29:32.255: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158232819s
Jun  7 16:29:34.290: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193323781s
... skipping 10 lines ...
Jun  7 16:29:56.636: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 32.539790125s
Jun  7 16:29:58.668: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 34.571525292s
Jun  7 16:30:00.699: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 36.602915436s
Jun  7 16:30:02.731: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Pending", Reason="", readiness=false. Elapsed: 38.63488282s
Jun  7 16:30:04.764: INFO: Pod "pod-subpath-test-dynamicpv-kx9z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.667006163s
STEP: Saw pod success
Jun  7 16:30:04.764: INFO: Pod "pod-subpath-test-dynamicpv-kx9z" satisfied condition "Succeeded or Failed"
Jun  7 16:30:04.794: INFO: Trying to get logs from node ip-172-20-55-190.ec2.internal pod pod-subpath-test-dynamicpv-kx9z container test-container-subpath-dynamicpv-kx9z: <nil>
STEP: delete the pod
Jun  7 16:30:04.866: INFO: Waiting for pod pod-subpath-test-dynamicpv-kx9z to disappear
Jun  7 16:30:04.897: INFO: Pod pod-subpath-test-dynamicpv-kx9z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kx9z
Jun  7 16:30:04.897: INFO: Deleting pod "pod-subpath-test-dynamicpv-kx9z" in namespace "provisioning-4631"
... skipping 133 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:04.100: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:30:04.261: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 16:30:04.261: INFO: Creating resource for dynamic PV
Jun  7 16:30:04.262: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-477sjmlb
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:30:12.510: INFO: Deleting pod "pod-67916705-68e9-464f-900f-b9bcf7847632" in namespace "volumemode-477"
Jun  7 16:30:12.543: INFO: Wait up to 5m0s for pod "pod-67916705-68e9-464f-900f-b9bcf7847632" to be fully deleted
STEP: Deleting pvc
Jun  7 16:30:18.675: INFO: Deleting PersistentVolumeClaim "awsx5bfr"
Jun  7 16:30:18.714: INFO: Waiting up to 5m0s for PersistentVolume pvc-70522743-477f-4f85-906a-c9448cf1dc1e to get deleted
Jun  7 16:30:18.744: INFO: PersistentVolume pvc-70522743-477f-4f85-906a-c9448cf1dc1e found and phase=Released (30.630194ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:33.934: INFO: >>> kubeConfig: /root/.kube/config
... skipping 73 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:29:40.093: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  7 16:29:40.246: INFO: Creating resource for dynamic PV
Jun  7 16:29:40.246: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7212-e2e-scjqw2p
STEP: creating a claim
Jun  7 16:29:40.277: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x4g6
STEP: Checking for subpath error in container status
Jun  7 16:30:18.431: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4g6" in namespace "provisioning-7212"
Jun  7 16:30:18.462: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-x4g6" to be fully deleted
STEP: Deleting pod
Jun  7 16:30:24.523: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4g6" in namespace "provisioning-7212"
STEP: Deleting pvc
Jun  7 16:30:24.614: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comkm4w9"
... skipping 10 lines ...

• [SLOW TEST:54.745 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 16:30:34.839: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 351 lines ...

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

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

    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:03.658: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  7 16:30:03.815: INFO: Creating resource for dynamic PV
Jun  7 16:30:03.815: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9079-e2e-sckzjm9
STEP: creating a claim
Jun  7 16:30:03.851: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l8k9
STEP: Checking for subpath error in container status
Jun  7 16:30:28.013: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8k9" in namespace "provisioning-9079"
Jun  7 16:30:28.045: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l8k9" to be fully deleted
STEP: Deleting pod
Jun  7 16:30:40.107: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8k9" in namespace "provisioning-9079"
STEP: Deleting pvc
Jun  7 16:30:40.207: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comv7zwh"
... skipping 10 lines ...

• [SLOW TEST:46.778 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  7 16:30:15.028: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7855prbc6
STEP: creating a claim
Jun  7 16:30:15.064: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j5hr
STEP: Creating a pod to test subpath
Jun  7 16:30:15.159: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j5hr" in namespace "provisioning-7855" to be "Succeeded or Failed"
Jun  7 16:30:15.190: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 30.290762ms
Jun  7 16:30:17.221: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06149153s
Jun  7 16:30:19.254: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094559418s
Jun  7 16:30:21.287: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127674927s
Jun  7 16:30:23.319: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159379394s
Jun  7 16:30:25.350: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190412201s
Jun  7 16:30:27.381: INFO: Pod "pod-subpath-test-dynamicpv-j5hr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.221712901s
STEP: Saw pod success
Jun  7 16:30:27.381: INFO: Pod "pod-subpath-test-dynamicpv-j5hr" satisfied condition "Succeeded or Failed"
Jun  7 16:30:27.411: INFO: Trying to get logs from node ip-172-20-51-74.ec2.internal pod pod-subpath-test-dynamicpv-j5hr container test-container-subpath-dynamicpv-j5hr: <nil>
STEP: delete the pod
Jun  7 16:30:27.485: INFO: Waiting for pod pod-subpath-test-dynamicpv-j5hr to disappear
Jun  7 16:30:27.515: INFO: Pod pod-subpath-test-dynamicpv-j5hr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j5hr
Jun  7 16:30:27.515: INFO: Deleting pod "pod-subpath-test-dynamicpv-j5hr" in namespace "provisioning-7855"
... skipping 606 lines ...
Jun  7 16:30:34.995: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9484-e2e-sc4xmdp
STEP: creating a claim
Jun  7 16:30:35.027: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  7 16:30:35.089: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 16:30:35.150: INFO: Error updating pvc ebs.csi.aws.comzbtdj: PersistentVolumeClaim "ebs.csi.aws.comzbtdj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9484-e2e-sc4xmdp",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  7 16:31:05.287: INFO: Error updating pvc ebs.csi.aws.comzbtdj: PersistentVolumeClaim "ebs.csi.aws.comzbtdj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 103 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:16.775: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  7 16:30:16.936: INFO: Creating resource for dynamic PV
Jun  7 16:30:16.936: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4903-e2e-scrzx6g
STEP: creating a claim
Jun  7 16:30:16.969: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z8rm
STEP: Checking for subpath error in container status
Jun  7 16:30:41.130: INFO: Deleting pod "pod-subpath-test-dynamicpv-z8rm" in namespace "provisioning-4903"
Jun  7 16:30:41.163: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z8rm" to be fully deleted
STEP: Deleting pod
Jun  7 16:30:49.225: INFO: Deleting pod "pod-subpath-test-dynamicpv-z8rm" in namespace "provisioning-4903"
STEP: Deleting pvc
Jun  7 16:30:49.321: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4czxd"
... skipping 12 lines ...

• [SLOW TEST:52.849 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 16:30:37.977: 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 16:30:38.133: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 16:30:38.673: INFO: Successfully created a new PD: "aws://us-east-1a/vol-096efcffa926f6b48".
Jun  7 16:30:38.674: INFO: Creating resource for pre-provisioned PV
Jun  7 16:30:38.674: INFO: Creating PVC and PV
... skipping 2 lines ...
Jun  7 16:30:38.832: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-q59fl] to have phase Bound
Jun  7 16:30:38.863: INFO: PersistentVolumeClaim pvc-q59fl found but phase is Pending instead of Bound.
Jun  7 16:30:40.895: INFO: PersistentVolumeClaim pvc-q59fl found and phase=Bound (2.062641936s)
Jun  7 16:30:40.895: INFO: Waiting up to 3m0s for PersistentVolume aws-mvmg9 to have phase Bound
Jun  7 16:30:40.927: INFO: PersistentVolume aws-mvmg9 found and phase=Bound (31.515971ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 16:30:43.123: INFO: Deleting pod "pod-9a24abae-a030-46b5-a23e-9c58cd18a6b2" in namespace "volumemode-10"
Jun  7 16:30:43.158: INFO: Wait up to 5m0s for pod "pod-9a24abae-a030-46b5-a23e-9c58cd18a6b2" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 16:30:53.221: INFO: Deleting PersistentVolumeClaim "pvc-q59fl"
Jun  7 16:30:53.276: INFO: Deleting PersistentVolume "aws-mvmg9"
Jun  7 16:30:53.501: INFO: Couldn't delete PD "aws://us-east-1a/vol-096efcffa926f6b48", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-096efcffa926f6b48 is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: 6714680d-ff90-46d6-8f3f-06304a5f7550
Jun  7 16:30:58.979: INFO: Couldn't delete PD "aws://us-east-1a/vol-096efcffa926f6b48", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-096efcffa926f6b48 is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: da6263a9-6b68-425b-a5dd-2d786da00d73
Jun  7 16:31:04.323: INFO: Couldn't delete PD "aws://us-east-1a/vol-096efcffa926f6b48", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-096efcffa926f6b48 is currently attached to i-08f3176b1faacacc6
	status code: 400, request id: 26213183-3e05-48fb-8699-f880f8654c1b
Jun  7 16:31:09.662: INFO: Successfully deleted PD "aws://us-east-1a/vol-096efcffa926f6b48".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 16:31:09.662: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-10" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.lyccc3Uj6/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 188 lines ...
Jun  7 16:28:32.811: INFO: Creating resource for dynamic PV
Jun  7 16:28:32.811: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2520-e2e-schlb7c
STEP: creating a claim
Jun  7 16:28:32.845: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 16:28:32.942: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cjvk8" in namespace "snapshotting-2520" to be "Succeeded or Failed"
Jun  7 16:28:32.972: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.369952ms
Jun  7 16:28:35.005: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062904118s
Jun  7 16:28:37.037: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095048781s
Jun  7 16:28:39.070: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128199004s
Jun  7 16:28:41.109: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16711089s
Jun  7 16:28:43.143: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201028318s
Jun  7 16:28:45.175: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.233017697s
Jun  7 16:28:47.212: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.270073612s
Jun  7 16:28:49.243: INFO: Pod "pvc-snapshottable-tester-cjvk8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.300887583s
STEP: Saw pod success
Jun  7 16:28:49.243: INFO: Pod "pvc-snapshottable-tester-cjvk8" satisfied condition "Succeeded or Failed"
Jun  7 16:28:49.305: INFO: Pod pvc-snapshottable-tester-cjvk8 has the following logs: 
Jun  7 16:28:49.305: INFO: Deleting pod "pvc-snapshottable-tester-cjvk8" in namespace "snapshotting-2520"
Jun  7 16:28:49.342: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-cjvk8" to be fully deleted
Jun  7 16:28:49.375: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com4wqb8] to have phase Bound
Jun  7 16:28:49.405: INFO: PersistentVolumeClaim ebs.csi.aws.com4wqb8 found and phase=Bound (30.281799ms)
STEP: [init] checking the claim
... skipping 20 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.lyccc3Uj6/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  7 16:29:10.102: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-qqzrr" in namespace "snapshotting-2520" to be "Succeeded or Failed"
Jun  7 16:29:10.133: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 30.222062ms
Jun  7 16:29:12.164: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061959848s
Jun  7 16:29:14.195: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092848463s
Jun  7 16:29:16.228: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125761067s
Jun  7 16:29:18.260: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157298295s
Jun  7 16:29:20.291: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188243846s
... skipping 23 lines ...
Jun  7 16:30:09.067: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 58.964266702s
Jun  7 16:30:11.112: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.009429009s
Jun  7 16:30:13.142: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.039717176s
Jun  7 16:30:15.176: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.073490898s
Jun  7 16:30:17.207: INFO: Pod "pvc-snapshottable-data-tester-qqzrr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.104190443s
STEP: Saw pod success
Jun  7 16:30:17.207: INFO: Pod "pvc-snapshottable-data-tester-qqzrr" satisfied condition "Succeeded or Failed"
Jun  7 16:30:17.269: INFO: Pod pvc-snapshottable-data-tester-qqzrr has the following logs: 
Jun  7 16:30:17.269: INFO: Deleting pod "pvc-snapshottable-data-tester-qqzrr" in namespace "snapshotting-2520"
Jun  7 16:30:17.309: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-qqzrr" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 16:30:33.473: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2520 exec restored-pvc-tester-zg4ps --namespace=snapshotting-2520 -- cat /mnt/test/data'
... skipping 36 lines ...
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:36 +0000 UTC - event for ebs.csi.aws.com4wqb8: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-8sp8f_015d1470-6350-4596-9122-6d040bee6282 } ProvisioningSucceeded: Successfully provisioned volume pvc-f7837f17-8647-4485-8b4b-76498cecc35e
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:45 +0000 UTC - event for pvc-snapshottable-tester-cjvk8: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-f7837f17-8647-4485-8b4b-76498cecc35e" 
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:47 +0000 UTC - event for pvc-snapshottable-tester-cjvk8: {kubelet ip-172-20-51-74.ec2.internal} Created: Created container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:47 +0000 UTC - event for pvc-snapshottable-tester-cjvk8: {kubelet ip-172-20-51-74.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:47 +0000 UTC - event for pvc-snapshottable-tester-cjvk8: {kubelet ip-172-20-51-74.ec2.internal} Started: Started container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:28:49 +0000 UTC - event for snapshot-gt4zq: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-2520/snapshot-gt4zq to be created by the CSI driver.
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:29:13 +0000 UTC - event for pvc-snapshottable-data-tester-qqzrr: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "pvc-f7837f17-8647-4485-8b4b-76498cecc35e" Volume is already exclusively attached to one node and can't be attached to another
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:29:42 +0000 UTC - event for pvc-snapshottable-data-tester-qqzrr: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-f7837f17-8647-4485-8b4b-76498cecc35e" 
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:14 +0000 UTC - event for pvc-snapshottable-data-tester-qqzrr: {kubelet ip-172-20-55-190.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:15 +0000 UTC - event for pvc-snapshottable-data-tester-qqzrr: {kubelet ip-172-20-55-190.ec2.internal} Created: Created container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:15 +0000 UTC - event for pvc-snapshottable-data-tester-qqzrr: {kubelet ip-172-20-55-190.ec2.internal} Started: Started container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:17 +0000 UTC - event for pvc-27hfp: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-8sp8f_015d1470-6350-4596-9122-6d040bee6282 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-2520/pvc-27hfp"
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:17 +0000 UTC - event for pvc-27hfp: {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  7 16:31:27.629: INFO: At 2021-06-07 16:30:17 +0000 UTC - event for pvc-27hfp: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:21 +0000 UTC - event for pvc-27hfp: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-8sp8f_015d1470-6350-4596-9122-6d040bee6282 } ProvisioningSucceeded: Successfully provisioned volume pvc-743f349a-76e0-4d31-8a0e-3b711889fdc8
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:29 +0000 UTC - event for restored-pvc-tester-zg4ps: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-743f349a-76e0-4d31-8a0e-3b711889fdc8" 
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:31 +0000 UTC - event for restored-pvc-tester-zg4ps: {kubelet ip-172-20-55-190.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:31 +0000 UTC - event for restored-pvc-tester-zg4ps: {kubelet ip-172-20-55-190.ec2.internal} Created: Created container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:31 +0000 UTC - event for restored-pvc-tester-zg4ps: {kubelet ip-172-20-55-190.ec2.internal} Started: Started container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:30:34 +0000 UTC - event for restored-pvc-tester-zg4ps: {kubelet ip-172-20-55-190.ec2.internal} Killing: Stopping container volume-tester
Jun  7 16:31:27.629: INFO: At 2021-06-07 16:31:18 +0000 UTC - event for snapshot-gt4zq: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-2520/snapshot-gt4zq on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "snapshot-gt4zq": the object has been modified; please apply your changes to the latest version and try again
Jun  7 16:31:27.659: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun  7 16:31:27.659: INFO: 
Jun  7 16:31:27.690: INFO: 
Logging node info for node ip-172-20-36-23.ec2.internal
Jun  7 16:31:27.720: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-36-23.ec2.internal    75a14fb5-e308-4dc8-b176-a7302baa4601 15936 0 2021-06-07 16:19:27 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a kops.k8s.io/instancegroup:nodes-us-east-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-36-23.ec2.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-1a topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0637bb7144cc4016d"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.36.23/19 projectcalico.org/IPv4IPIPTunnelAddr:100.101.161.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-07 16:19:27 +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-07 16:19:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-06-07 16:30:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}}} {kubelet Update v1 2021-06-07 16:31:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-0637bb7144cc4016d,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{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-07 16:19:45 +0000 UTC,LastTransitionTime:2021-06-07 16:19:45 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-07 16:31:18 +0000 UTC,LastTransitionTime:2021-06-07 16:19:27 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-07 16:31:18 +0000 UTC,LastTransitionTime:2021-06-07 16:19:27 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-07 16:31:18 +0000 UTC,LastTransitionTime:2021-06-07 16:19:27 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-07 16:31:18 +0000 UTC,LastTransitionTime:2021-06-07 16:19:47 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.36.23,},NodeAddress{Type:ExternalIP,Address:54.221.132.126,},NodeAddress{Type:Hostname,Address:ip-172-20-36-23.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-36-23.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-221-132-126.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec27c23f66bf5c534f72ead91fcce4ff,SystemUUID:ec27c23f-66bf-5c53-4f72-ead91fcce4ff,BootID:194da424-e320-4d9d-81c9-61eb66229deb,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[quay.io/jetstack/cert-manager-webhook@sha256:41eacd93a30b566b780a6ae525b2547d2a87f1ec5f067fc02840a220aeb0c3f7 quay.io/jetstack/cert-manager-webhook:v1.3.1],SizeBytes:19734169,},ContainerImage{Names:[quay.io/jetstack/cert-manager-cainjector@sha256:51c0df411b66aa175e9fc6840f3135d55b52c3781d0b3d4aa10862066d460193 quay.io/jetstack/cert-manager-cainjector:v1.3.1],SizeBytes:19215137,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jun  7 16:31:27.721: INFO: 
... skipping 172 lines ...
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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-2520 exec restored-pvc-tester-zg4ps --namespace=snapshotting-2520 -- 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-2520 exec restored-pvc-tester-zg4ps --namespace=snapshotting-2520 -- 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
... skipping 912 lines ...
Jun  7 16:30:38.215: INFO: Creating resource for dynamic PV
Jun  7 16:30:38.215: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8860-e2e-scwjkn9
STEP: creating a claim
Jun  7 16:30:38.247: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 16:30:38.345: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-dj64h" in namespace "snapshotting-8860" to be "Succeeded or Failed"
Jun  7 16:30:38.379: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 33.921717ms
Jun  7 16:30:40.411: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06624887s
Jun  7 16:30:42.443: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098026665s
Jun  7 16:30:44.476: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130483252s
Jun  7 16:30:46.508: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.1632582s
Jun  7 16:30:48.540: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194820651s
Jun  7 16:30:50.572: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.227351844s
Jun  7 16:30:52.605: INFO: Pod "pvc-snapshottable-tester-dj64h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.259503844s
STEP: Saw pod success
Jun  7 16:30:52.605: INFO: Pod "pvc-snapshottable-tester-dj64h" satisfied condition "Succeeded or Failed"
Jun  7 16:30:52.670: INFO: Pod pvc-snapshottable-tester-dj64h has the following logs: 
Jun  7 16:30:52.670: INFO: Deleting pod "pvc-snapshottable-tester-dj64h" in namespace "snapshotting-8860"
Jun  7 16:30:52.707: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-dj64h" to be fully deleted
Jun  7 16:30:52.738: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com8mls4] to have phase Bound
Jun  7 16:30:52.770: INFO: PersistentVolumeClaim ebs.csi.aws.com8mls4 found and phase=Bound (31.341174ms)
STEP: [init] checking the claim
... skipping 38 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.lyccc3Uj6/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  7 16:31:50.064: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-zmgl8" in namespace "snapshotting-8860" to be "Succeeded or Failed"
Jun  7 16:31:50.096: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.695219ms
Jun  7 16:31:52.128: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063833966s
Jun  7 16:31:54.161: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096301524s
Jun  7 16:31:56.194: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129470566s
Jun  7 16:31:58.226: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161714092s
Jun  7 16:32:00.260: INFO: Pod "pvc-snapshottable-data-tester-zmgl8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.195033055s
STEP: Saw pod success
Jun  7 16:32:00.260: INFO: Pod "pvc-snapshottable-data-tester-zmgl8" satisfied condition "Succeeded or Failed"
Jun  7 16:32:00.326: INFO: Pod pvc-snapshottable-data-tester-zmgl8 has the following logs: 
Jun  7 16:32:00.326: INFO: Deleting pod "pvc-snapshottable-data-tester-zmgl8" in namespace "snapshotting-8860"
Jun  7 16:32:00.368: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-zmgl8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 16:32:10.529: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8860 exec restored-pvc-tester-7fgc6 --namespace=snapshotting-8860 -- cat /mnt/test/data'
... skipping 220 lines ...
    /tmp/kops.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.lyccc3Uj6/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.lyccc3Uj6/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-8860 exec restored-pvc-tester-7fgc6 --namespace=snapshotting-8860 -- 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-8860 exec restored-pvc-tester-7fgc6 --namespace=snapshotting-8860 -- 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.lyccc3Uj6/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------


Summarizing 2 Failures:

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

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

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


Ginkgo ran 1 suite in 11m7.690469243s
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
I0607 16:33:04.570303   26727 app.go:59] RunDir for this run: "/logs/artifacts/b03c9a69-c7a9-11eb-a95e-22b332769ebd"
I0607 16:33:04.570454   26727 app.go:90] ID for this run: "b03c9a69-c7a9-11eb-a95e-22b332769ebd"
I0607 16:33:04.570480   26727 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
I0607 16:33:04.586222   26733 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1443 lines ...