This job view page is being replaced by Spyglass soon. Check out the new job view.
PReddycharly: feat: add support for custom audience in aws oidc provider
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-27 08:51
Elapsed1h17m
Revision77b92960f75e2c807b849d370d6fee7aef74265e
Refs 12419

No Test Failures!


Error lines from build-log.txt

... skipping 556 lines ...
I0927 08:56:12.119855   12508 app.go:90] ID for this run: "12325842-1f70-11ec-8af3-22f8e8a1ce5c"
I0927 08:56:12.165497   12508 up.go:43] Cleaning up any leaked resources from previous cluster
I0927 08:56:12.165618   12508 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0927 08:56:12.204408   12518 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 08:56:12.204530   12518 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 08:56:12.204544   12518 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
W0927 08:56:12.764346   12508 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0927 08:56:12.764513   12508 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --yes
I0927 08:56:12.801127   12529 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 08:56:12.801244   12529 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 08:56:12.801248   12529 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
I0927 08:56:13.295219   12508 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/27 08:56:13 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
I0927 08:56:13.307161   12508 http.go:37] curl https://ip.jsb.workers.dev
I0927 08:56:13.440067   12508 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.132.118.163/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0927 08:56:13.477895   12542 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 08:56:13.478051   12542 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 08:56:13.478056   12542 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 08:56:13.533240   12542 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 31 lines ...
I0927 08:56:33.762813   12508 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0927 08:56:33.798593   12563 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 08:56:33.798695   12563 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 08:56:33.798703   12563 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io

W0927 08:56:35.633720   12563 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:56:45.666478   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
W0927 08:56:55.699609   12563 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:05.735980   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:15.772529   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:25.801652   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:35.845511   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:45.877093   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:57:55.909074   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:05.939898   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:15.976469   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:26.021521   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:36.053240   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:46.084179   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:58:56.114413   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:06.149485   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:16.232678   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:26.269846   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:36.307056   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:46.337283   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 08:59:56.381963   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 09:00:06.426989   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 09:00:16.474012   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 09:00:26.503661   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 09:00:36.536455   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 09:00:46.571567   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 26 lines ...
Pod	kube-system/ebs-csi-node-fqcmc						system-node-critical pod "ebs-csi-node-fqcmc" is pending
Pod	kube-system/ebs-csi-node-tdlgr						system-node-critical pod "ebs-csi-node-tdlgr" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-234.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-234.ap-south-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-172.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-172.ap-south-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-163.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-163.ap-south-1.compute.internal" is pending

Validation Failed
W0927 09:01:01.965663   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-556s5						system-node-critical pod "ebs-csi-node-556s5" is pending
Pod	kube-system/ebs-csi-node-7999f						system-node-critical pod "ebs-csi-node-7999f" is pending
Pod	kube-system/ebs-csi-node-fqcmc						system-node-critical pod "ebs-csi-node-fqcmc" is pending
Pod	kube-system/ebs-csi-node-tdlgr						system-node-critical pod "ebs-csi-node-tdlgr" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-163.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-163.ap-south-1.compute.internal" is pending

Validation Failed
W0927 09:01:15.600999   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-54rl4			system-node-critical pod "ebs-csi-node-54rl4" is pending
Pod	kube-system/ebs-csi-node-556s5			system-node-critical pod "ebs-csi-node-556s5" is pending
Pod	kube-system/ebs-csi-node-7999f			system-node-critical pod "ebs-csi-node-7999f" is pending
Pod	kube-system/ebs-csi-node-fqcmc			system-node-critical pod "ebs-csi-node-fqcmc" is pending
Pod	kube-system/ebs-csi-node-tdlgr			system-node-critical pod "ebs-csi-node-tdlgr" is pending

Validation Failed
W0927 09:01:29.245215   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-54rl4	system-node-critical pod "ebs-csi-node-54rl4" is pending
Pod	kube-system/ebs-csi-node-7999f	system-node-critical pod "ebs-csi-node-7999f" is pending

Validation Failed
W0927 09:01:42.902130   12563 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 194 lines ...

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 93 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:05:21.196: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 09:05:22.641: INFO: found topology map[topology.kubernetes.io/zone:ap-south-1a]
Sep 27 09:05:22.642: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:05:22.642: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 35 lines ...
Sep 27 09:05:21.968: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 09:05:23.171: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-0b4e7b47becefa231".
Sep 27 09:05:23.171: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lpfh
STEP: Creating a pod to test exec-volume-test
Sep 27 09:05:23.419: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lpfh" in namespace "volume-4591" to be "Succeeded or Failed"
Sep 27 09:05:23.671: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 252.690142ms
Sep 27 09:05:25.919: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.499969524s
Sep 27 09:05:28.165: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.746023213s
Sep 27 09:05:30.410: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.991534419s
Sep 27 09:05:32.657: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 9.238055281s
Sep 27 09:05:34.903: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Pending", Reason="", readiness=false. Elapsed: 11.484198635s
Sep 27 09:05:37.150: INFO: Pod "exec-volume-test-inlinevolume-lpfh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.731584206s
STEP: Saw pod success
Sep 27 09:05:37.150: INFO: Pod "exec-volume-test-inlinevolume-lpfh" satisfied condition "Succeeded or Failed"
Sep 27 09:05:37.396: INFO: Trying to get logs from node ip-172-20-51-172.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-lpfh container exec-container-inlinevolume-lpfh: <nil>
STEP: delete the pod
Sep 27 09:05:37.914: INFO: Waiting for pod exec-volume-test-inlinevolume-lpfh to disappear
Sep 27 09:05:38.160: INFO: Pod exec-volume-test-inlinevolume-lpfh no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lpfh
Sep 27 09:05:38.160: INFO: Deleting pod "exec-volume-test-inlinevolume-lpfh" in namespace "volume-4591"
Sep 27 09:05:38.802: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0b4e7b47becefa231", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b4e7b47becefa231 is currently attached to i-01936d56116684286
	status code: 400, request id: 996e32fd-6be6-4643-86eb-3c76a7fec5ee
Sep 27 09:05:44.913: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0b4e7b47becefa231".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:05:44.913: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4591" for this suite.
... skipping 58 lines ...
STEP: Creating a kubernetes client
Sep 27 09:05:16.560: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0927 09:05:18.844770   25330 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 27 09:05:18.844: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:05:19.327: INFO: Creating resource for dynamic PV
Sep 27 09:05:19.327: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1310-e2e-sch5hvn
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:05:25.028: INFO: Deleting pod "pod-0dcc0d18-de2b-4110-b549-fa699fb21318" in namespace "volumemode-1310"
Sep 27 09:05:25.277: INFO: Wait up to 5m0s for pod "pod-0dcc0d18-de2b-4110-b549-fa699fb21318" to be fully deleted
STEP: Deleting pvc
Sep 27 09:05:28.248: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxbk26"
Sep 27 09:05:28.492: INFO: Waiting up to 5m0s for PersistentVolume pvc-ad07e3c5-b8e1-435f-90a5-46603d9b6e4c to get deleted
Sep 27 09:05:28.735: INFO: PersistentVolume pvc-ad07e3c5-b8e1-435f-90a5-46603d9b6e4c found and phase=Released (243.321316ms)
... skipping 9 lines ...

• [SLOW TEST:28.868 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Volume Placement [Feature:vsphere]
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:05:45.430: INFO: >>> kubeConfig: /root/.kube/config
... skipping 58 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:05:19.140: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:05:20.367: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:05:20.367: INFO: Creating resource for dynamic PV
Sep 27 09:05:20.367: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9994wjcgl
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:05:28.039: INFO: Deleting pod "pod-1e844518-5eeb-4ae5-8aea-99878f6d0348" in namespace "volumemode-9994"
Sep 27 09:05:28.277: INFO: Wait up to 5m0s for pod "pod-1e844518-5eeb-4ae5-8aea-99878f6d0348" to be fully deleted
STEP: Deleting pvc
Sep 27 09:05:31.228: INFO: Deleting PersistentVolumeClaim "awsbk7s7"
Sep 27 09:05:31.466: INFO: Waiting up to 5m0s for PersistentVolume pvc-6ed35575-8519-41c2-9326-69e9f7a090dd to get deleted
Sep 27 09:05:31.705: INFO: PersistentVolume pvc-6ed35575-8519-41c2-9326-69e9f7a090dd found and phase=Released (238.649109ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 73 lines ...
STEP: Creating a kubernetes client
Sep 27 09:05:16.460: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0927 09:05:17.994590   25234 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 27 09:05:17.994: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:05:18.483: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:05:18.483: INFO: Creating resource for dynamic PV
Sep 27 09:05:18.483: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-640722k4k
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:05:24.213: INFO: Deleting pod "pod-8b1d8d03-00d2-493e-81e3-0b5b537d7348" in namespace "volumemode-6407"
Sep 27 09:05:24.483: INFO: Wait up to 5m0s for pod "pod-8b1d8d03-00d2-493e-81e3-0b5b537d7348" to be fully deleted
STEP: Deleting pvc
Sep 27 09:05:27.468: INFO: Deleting PersistentVolumeClaim "awsn4zrt"
Sep 27 09:05:27.714: INFO: Waiting up to 5m0s for PersistentVolume pvc-38e8baac-6295-46d8-aa16-2c0b06410ac5 to get deleted
Sep 27 09:05:27.959: INFO: PersistentVolume pvc-38e8baac-6295-46d8-aa16-2c0b06410ac5 found and phase=Released (244.993663ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 09:05:49.931: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

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

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

    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 43 lines ...
Sep 27 09:05:18.240: INFO: Creating resource for dynamic PV
Sep 27 09:05:18.240: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8420-e2e-scw9cwk
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 27 09:05:18.959: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 09:05:19.445: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:21.922: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:23.921: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:25.920: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:27.921: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:29.932: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:31.920: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:33.921: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:35.920: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:37.923: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:39.920: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:41.920: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:43.921: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:45.924: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:47.922: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:49.926: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8420-e2e-scw9cwk",
  	... // 3 identical fields
  }

Sep 27 09:05:50.400: INFO: Error updating pvc ebs.csi.aws.comdn7xt: PersistentVolumeClaim "ebs.csi.aws.comdn7xt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 41 lines ...
Sep 27 09:05:18.439: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5182-e2e-sczt6s4
STEP: creating a claim
Sep 27 09:05:18.690: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qsch
STEP: Creating a pod to test multi_subpath
Sep 27 09:05:19.435: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qsch" in namespace "provisioning-5182" to be "Succeeded or Failed"
Sep 27 09:05:19.676: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 240.741807ms
Sep 27 09:05:21.917: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 2.482142016s
Sep 27 09:05:24.167: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 4.731747211s
Sep 27 09:05:26.413: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 6.977446424s
Sep 27 09:05:28.654: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 9.218635892s
Sep 27 09:05:30.896: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 11.460950669s
Sep 27 09:05:33.137: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 13.702061821s
Sep 27 09:05:35.379: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 15.943320693s
Sep 27 09:05:37.620: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 18.1843679s
Sep 27 09:05:39.860: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Pending", Reason="", readiness=false. Elapsed: 20.42511329s
Sep 27 09:05:42.101: INFO: Pod "pod-subpath-test-dynamicpv-qsch": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.6658053s
STEP: Saw pod success
Sep 27 09:05:42.101: INFO: Pod "pod-subpath-test-dynamicpv-qsch" satisfied condition "Succeeded or Failed"
Sep 27 09:05:42.342: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-qsch container test-container-subpath-dynamicpv-qsch: <nil>
STEP: delete the pod
Sep 27 09:05:42.857: INFO: Waiting for pod pod-subpath-test-dynamicpv-qsch to disappear
Sep 27 09:05:43.097: INFO: Pod pod-subpath-test-dynamicpv-qsch no longer exists
STEP: Deleting pod
Sep 27 09:05:43.097: INFO: Deleting pod "pod-subpath-test-dynamicpv-qsch" in namespace "provisioning-5182"
... skipping 73 lines ...
Sep 27 09:05:21.410: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5937-e2e-scxlw76
STEP: creating a claim
Sep 27 09:05:21.656: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9t89
STEP: Creating a pod to test exec-volume-test
Sep 27 09:05:22.395: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9t89" in namespace "volume-5937" to be "Succeeded or Failed"
Sep 27 09:05:22.640: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 244.743945ms
Sep 27 09:05:24.887: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492096178s
Sep 27 09:05:27.133: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 4.738332054s
Sep 27 09:05:29.380: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 6.984789364s
Sep 27 09:05:31.626: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 9.23109986s
Sep 27 09:05:33.874: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 11.478966237s
... skipping 3 lines ...
Sep 27 09:05:42.864: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 20.468793427s
Sep 27 09:05:45.113: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 22.718412286s
Sep 27 09:05:47.359: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 24.963765209s
Sep 27 09:05:49.604: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Pending", Reason="", readiness=false. Elapsed: 27.209057902s
Sep 27 09:05:51.850: INFO: Pod "exec-volume-test-dynamicpv-9t89": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.45506883s
STEP: Saw pod success
Sep 27 09:05:51.850: INFO: Pod "exec-volume-test-dynamicpv-9t89" satisfied condition "Succeeded or Failed"
Sep 27 09:05:52.095: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-9t89 container exec-container-dynamicpv-9t89: <nil>
STEP: delete the pod
Sep 27 09:05:52.603: INFO: Waiting for pod exec-volume-test-dynamicpv-9t89 to disappear
Sep 27 09:05:52.848: INFO: Pod exec-volume-test-dynamicpv-9t89 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9t89
Sep 27 09:05:52.848: INFO: Deleting pod "exec-volume-test-dynamicpv-9t89" in namespace "volume-5937"
... skipping 148 lines ...
Sep 27 09:05:20.241: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4439fx8b9
STEP: creating a claim
Sep 27 09:05:20.481: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rkjk
STEP: Creating a pod to test subpath
Sep 27 09:05:21.208: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rkjk" in namespace "provisioning-4439" to be "Succeeded or Failed"
Sep 27 09:05:21.446: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 237.728827ms
Sep 27 09:05:23.685: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476256737s
Sep 27 09:05:25.922: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.713595322s
Sep 27 09:05:28.161: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.952673756s
Sep 27 09:05:30.400: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 9.191541666s
Sep 27 09:05:32.638: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 11.429560513s
... skipping 3 lines ...
Sep 27 09:05:41.591: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.382276934s
Sep 27 09:05:43.830: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.621746351s
Sep 27 09:05:46.069: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.860929705s
Sep 27 09:05:48.307: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Pending", Reason="", readiness=false. Elapsed: 27.099103319s
Sep 27 09:05:50.553: INFO: Pod "pod-subpath-test-dynamicpv-rkjk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.344384984s
STEP: Saw pod success
Sep 27 09:05:50.553: INFO: Pod "pod-subpath-test-dynamicpv-rkjk" satisfied condition "Succeeded or Failed"
Sep 27 09:05:50.795: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-rkjk container test-container-subpath-dynamicpv-rkjk: <nil>
STEP: delete the pod
Sep 27 09:05:51.280: INFO: Waiting for pod pod-subpath-test-dynamicpv-rkjk to disappear
Sep 27 09:05:51.518: INFO: Pod pod-subpath-test-dynamicpv-rkjk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rkjk
Sep 27 09:05:51.519: INFO: Deleting pod "pod-subpath-test-dynamicpv-rkjk" in namespace "provisioning-4439"
... skipping 86 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 103 lines ...
Sep 27 09:05:18.463: INFO: Creating resource for dynamic PV
Sep 27 09:05:18.463: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3793t79q2
STEP: creating a claim
Sep 27 09:05:18.704: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3793
Sep 27 09:05:19.450: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3793" in namespace "provisioning-3793" to be "Succeeded or Failed"
Sep 27 09:05:19.691: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 240.935221ms
Sep 27 09:05:21.932: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 2.481867015s
Sep 27 09:05:24.176: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 4.72603224s
Sep 27 09:05:26.423: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 6.972793294s
Sep 27 09:05:28.664: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 9.213541721s
Sep 27 09:05:30.908: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 11.458496896s
Sep 27 09:05:33.149: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 13.699268285s
Sep 27 09:05:35.390: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 15.940027254s
Sep 27 09:05:37.631: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 18.1807515s
Sep 27 09:05:39.873: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 20.422614402s
Sep 27 09:05:42.113: INFO: Pod "volume-prep-provisioning-3793": Phase="Pending", Reason="", readiness=false. Elapsed: 22.663486537s
Sep 27 09:05:44.356: INFO: Pod "volume-prep-provisioning-3793": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.905662327s
STEP: Saw pod success
Sep 27 09:05:44.356: INFO: Pod "volume-prep-provisioning-3793" satisfied condition "Succeeded or Failed"
Sep 27 09:05:44.356: INFO: Deleting pod "volume-prep-provisioning-3793" in namespace "provisioning-3793"
Sep 27 09:05:44.607: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3793" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-k84d
STEP: Checking for subpath error in container status
Sep 27 09:06:07.570: INFO: Deleting pod "pod-subpath-test-dynamicpv-k84d" in namespace "provisioning-3793"
Sep 27 09:06:07.816: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-k84d" to be fully deleted
STEP: Deleting pod
Sep 27 09:06:08.057: INFO: Deleting pod "pod-subpath-test-dynamicpv-k84d" in namespace "provisioning-3793"
STEP: Deleting pvc
Sep 27 09:06:08.779: INFO: Deleting PersistentVolumeClaim "awsw2mlp"
... skipping 110 lines ...
Sep 27 09:05:18.665: INFO: Creating resource for dynamic PV
Sep 27 09:05:18.665: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6124-e2e-sctntnc
STEP: creating a claim
Sep 27 09:05:18.909: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6124
Sep 27 09:05:19.635: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6124" in namespace "provisioning-6124" to be "Succeeded or Failed"
Sep 27 09:05:19.876: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 240.530992ms
Sep 27 09:05:22.118: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 2.482706325s
Sep 27 09:05:24.367: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 4.731584881s
Sep 27 09:05:26.609: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 6.973806257s
Sep 27 09:05:28.852: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 9.217029739s
Sep 27 09:05:31.094: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 11.458701441s
Sep 27 09:05:33.335: INFO: Pod "volume-prep-provisioning-6124": Phase="Pending", Reason="", readiness=false. Elapsed: 13.699873238s
Sep 27 09:05:35.576: INFO: Pod "volume-prep-provisioning-6124": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.94086607s
STEP: Saw pod success
Sep 27 09:05:35.576: INFO: Pod "volume-prep-provisioning-6124" satisfied condition "Succeeded or Failed"
Sep 27 09:05:35.576: INFO: Deleting pod "volume-prep-provisioning-6124" in namespace "provisioning-6124"
Sep 27 09:05:35.821: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6124" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-tnng
STEP: Checking for subpath error in container status
Sep 27 09:05:58.793: INFO: Deleting pod "pod-subpath-test-dynamicpv-tnng" in namespace "provisioning-6124"
Sep 27 09:05:59.040: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tnng" to be fully deleted
STEP: Deleting pod
Sep 27 09:05:59.280: INFO: Deleting pod "pod-subpath-test-dynamicpv-tnng" in namespace "provisioning-6124"
STEP: Deleting pvc
Sep 27 09:06:00.002: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdczqt"
... skipping 132 lines ...
Sep 27 09:06:14.741: INFO: Waiting for pod aws-client to disappear
Sep 27 09:06:14.979: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 09:06:14.979: INFO: Deleting PersistentVolumeClaim "pvc-wcbz2"
Sep 27 09:06:15.217: INFO: Deleting PersistentVolume "aws-w2l59"
Sep 27 09:06:15.860: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05e1583527bb49dfc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05e1583527bb49dfc is currently attached to i-01936d56116684286
	status code: 400, request id: 8b8849e2-1881-4ff9-a3c2-228fc69287a8
Sep 27 09:06:21.966: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05e1583527bb49dfc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05e1583527bb49dfc is currently attached to i-01936d56116684286
	status code: 400, request id: 76f18e81-5403-4f9b-8e65-323bbc7b1027
Sep 27 09:06:28.169: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05e1583527bb49dfc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05e1583527bb49dfc is currently attached to i-01936d56116684286
	status code: 400, request id: 51c3080c-7479-426a-a289-abdb14eb522d
Sep 27 09:06:34.274: INFO: Successfully deleted PD "aws://ap-south-1a/vol-05e1583527bb49dfc".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:06:34.274: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9052" for this suite.
... skipping 24 lines ...
Sep 27 09:05:53.016: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-56294p4rc
STEP: creating a claim
Sep 27 09:05:53.254: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5xgc
STEP: Creating a pod to test subpath
Sep 27 09:05:53.971: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5xgc" in namespace "provisioning-5629" to be "Succeeded or Failed"
Sep 27 09:05:54.209: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 237.451222ms
Sep 27 09:05:56.447: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475886877s
Sep 27 09:05:58.685: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.713421673s
Sep 27 09:06:00.922: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.951138177s
Sep 27 09:06:03.160: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 9.188638073s
Sep 27 09:06:05.398: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 11.427110449s
Sep 27 09:06:07.636: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.66512944s
Sep 27 09:06:09.874: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 15.90240121s
Sep 27 09:06:12.112: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.141278025s
Sep 27 09:06:14.350: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 20.37862995s
Sep 27 09:06:16.587: INFO: Pod "pod-subpath-test-dynamicpv-5xgc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.615630192s
STEP: Saw pod success
Sep 27 09:06:16.587: INFO: Pod "pod-subpath-test-dynamicpv-5xgc" satisfied condition "Succeeded or Failed"
Sep 27 09:06:16.825: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-5xgc container test-container-volume-dynamicpv-5xgc: <nil>
STEP: delete the pod
Sep 27 09:06:17.313: INFO: Waiting for pod pod-subpath-test-dynamicpv-5xgc to disappear
Sep 27 09:06:17.550: INFO: Pod pod-subpath-test-dynamicpv-5xgc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5xgc
Sep 27 09:06:17.550: INFO: Deleting pod "pod-subpath-test-dynamicpv-5xgc" in namespace "provisioning-5629"
... skipping 32 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 30 lines ...
Sep 27 09:05:49.329: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3643-e2e-sc9lrjd
STEP: creating a claim
Sep 27 09:05:49.568: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-268f
STEP: Creating a pod to test subpath
Sep 27 09:05:50.284: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-268f" in namespace "provisioning-3643" to be "Succeeded or Failed"
Sep 27 09:05:50.523: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 238.45313ms
Sep 27 09:05:52.760: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475926243s
Sep 27 09:05:55.000: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.715554986s
Sep 27 09:05:57.237: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.953170479s
Sep 27 09:05:59.476: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 9.191429022s
Sep 27 09:06:01.714: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 11.429463944s
Sep 27 09:06:03.951: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 13.667166854s
Sep 27 09:06:06.192: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Pending", Reason="", readiness=false. Elapsed: 15.907753569s
Sep 27 09:06:08.429: INFO: Pod "pod-subpath-test-dynamicpv-268f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.145085073s
STEP: Saw pod success
Sep 27 09:06:08.429: INFO: Pod "pod-subpath-test-dynamicpv-268f" satisfied condition "Succeeded or Failed"
Sep 27 09:06:08.668: INFO: Trying to get logs from node ip-172-20-51-172.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-268f container test-container-subpath-dynamicpv-268f: <nil>
STEP: delete the pod
Sep 27 09:06:09.150: INFO: Waiting for pod pod-subpath-test-dynamicpv-268f to disappear
Sep 27 09:06:09.388: INFO: Pod pod-subpath-test-dynamicpv-268f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-268f
Sep 27 09:06:09.388: INFO: Deleting pod "pod-subpath-test-dynamicpv-268f" in namespace "provisioning-3643"
... skipping 364 lines ...
Sep 27 09:05:50.113: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3919-e2e-scp2z9l
STEP: creating a claim
Sep 27 09:05:50.359: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dznf
STEP: Creating a pod to test subpath
Sep 27 09:05:51.103: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dznf" in namespace "provisioning-3919" to be "Succeeded or Failed"
Sep 27 09:05:51.348: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 245.330823ms
Sep 27 09:05:53.594: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490750058s
Sep 27 09:05:55.840: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.736891354s
Sep 27 09:05:58.092: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.989506905s
Sep 27 09:06:00.340: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 9.236940454s
Sep 27 09:06:02.586: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 11.482776196s
... skipping 2 lines ...
Sep 27 09:06:09.324: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.220763496s
Sep 27 09:06:11.575: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.472598942s
Sep 27 09:06:13.822: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 22.719125389s
Sep 27 09:06:16.069: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Pending", Reason="", readiness=false. Elapsed: 24.965943847s
Sep 27 09:06:18.315: INFO: Pod "pod-subpath-test-dynamicpv-dznf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.212001549s
STEP: Saw pod success
Sep 27 09:06:18.315: INFO: Pod "pod-subpath-test-dynamicpv-dznf" satisfied condition "Succeeded or Failed"
Sep 27 09:06:18.560: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-dznf container test-container-volume-dynamicpv-dznf: <nil>
STEP: delete the pod
Sep 27 09:06:19.062: INFO: Waiting for pod pod-subpath-test-dynamicpv-dznf to disappear
Sep 27 09:06:19.307: INFO: Pod pod-subpath-test-dynamicpv-dznf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dznf
Sep 27 09:06:19.307: INFO: Deleting pod "pod-subpath-test-dynamicpv-dznf" in namespace "provisioning-3919"
... skipping 183 lines ...

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

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

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

    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 357 lines ...
Sep 27 09:06:41.118: INFO: Waiting for pod aws-client to disappear
Sep 27 09:06:41.358: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 09:06:41.358: INFO: Deleting PersistentVolumeClaim "pvc-wnwbj"
Sep 27 09:06:41.597: INFO: Deleting PersistentVolume "aws-f54pr"
Sep 27 09:06:42.964: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0251a499e7a0fb9ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0251a499e7a0fb9ad is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 5dc8f7f3-9fd0-4080-a3d0-4a0829f8897c
Sep 27 09:06:49.096: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0251a499e7a0fb9ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0251a499e7a0fb9ad is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: e4ffc094-ae09-43e3-a9f8-19c1358d9e6b
Sep 27 09:06:55.231: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0251a499e7a0fb9ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0251a499e7a0fb9ad is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 47e24786-5a4e-44b7-a0d0-81b6273f3128
Sep 27 09:07:01.360: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0251a499e7a0fb9ad".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:07:01.360: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4348" for this suite.
... skipping 160 lines ...
Sep 27 09:06:44.142: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 09:06:45.384: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-0a9a4d42dc3725ce5".
Sep 27 09:06:45.384: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-v6ng
STEP: Creating a pod to test exec-volume-test
Sep 27 09:06:45.625: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-v6ng" in namespace "volume-6730" to be "Succeeded or Failed"
Sep 27 09:06:45.862: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 237.103842ms
Sep 27 09:06:48.102: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476834475s
Sep 27 09:06:50.339: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 4.714153364s
Sep 27 09:06:52.579: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 6.954119476s
Sep 27 09:06:54.817: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 9.19237826s
Sep 27 09:06:57.058: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Pending", Reason="", readiness=false. Elapsed: 11.432862114s
Sep 27 09:06:59.296: INFO: Pod "exec-volume-test-inlinevolume-v6ng": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.671218555s
STEP: Saw pod success
Sep 27 09:06:59.296: INFO: Pod "exec-volume-test-inlinevolume-v6ng" satisfied condition "Succeeded or Failed"
Sep 27 09:06:59.534: INFO: Trying to get logs from node ip-172-20-63-190.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-v6ng container exec-container-inlinevolume-v6ng: <nil>
STEP: delete the pod
Sep 27 09:07:00.025: INFO: Waiting for pod exec-volume-test-inlinevolume-v6ng to disappear
Sep 27 09:07:00.262: INFO: Pod exec-volume-test-inlinevolume-v6ng no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-v6ng
Sep 27 09:07:00.262: INFO: Deleting pod "exec-volume-test-inlinevolume-v6ng" in namespace "volume-6730"
Sep 27 09:07:00.868: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0a9a4d42dc3725ce5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a9a4d42dc3725ce5 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: f691c80b-5be4-4f71-ac6a-b30a4bb61bd9
Sep 27 09:07:06.984: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0a9a4d42dc3725ce5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a9a4d42dc3725ce5 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 8a0e49d2-5193-43fe-afb7-49c44968b4b9
Sep 27 09:07:13.103: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0a9a4d42dc3725ce5".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:07:13.103: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6730" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 14 lines ...
Sep 27 09:06:49.328: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4529wmtd
STEP: creating a claim
Sep 27 09:06:49.566: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-xt29
STEP: Creating a pod to test exec-volume-test
Sep 27 09:06:50.278: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xt29" in namespace "volume-452" to be "Succeeded or Failed"
Sep 27 09:06:50.514: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 236.141623ms
Sep 27 09:06:52.751: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 2.472654615s
Sep 27 09:06:54.987: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 4.709289021s
Sep 27 09:06:57.225: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 6.946621863s
Sep 27 09:06:59.464: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 9.186020922s
Sep 27 09:07:01.701: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 11.423285163s
Sep 27 09:07:03.940: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 13.661901923s
Sep 27 09:07:06.177: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Pending", Reason="", readiness=false. Elapsed: 15.899292025s
Sep 27 09:07:08.415: INFO: Pod "exec-volume-test-dynamicpv-xt29": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.136655893s
STEP: Saw pod success
Sep 27 09:07:08.415: INFO: Pod "exec-volume-test-dynamicpv-xt29" satisfied condition "Succeeded or Failed"
Sep 27 09:07:08.651: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-xt29 container exec-container-dynamicpv-xt29: <nil>
STEP: delete the pod
Sep 27 09:07:09.137: INFO: Waiting for pod exec-volume-test-dynamicpv-xt29 to disappear
Sep 27 09:07:09.373: INFO: Pod exec-volume-test-dynamicpv-xt29 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xt29
Sep 27 09:07:09.373: INFO: Deleting pod "exec-volume-test-dynamicpv-xt29" in namespace "volume-452"
... skipping 314 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:06:34.988: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 27 09:06:36.184: INFO: Creating resource for dynamic PV
Sep 27 09:06:36.184: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4894-e2e-sclkb4z
STEP: creating a claim
Sep 27 09:06:36.430: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-shq6
STEP: Checking for subpath error in container status
Sep 27 09:07:17.622: INFO: Deleting pod "pod-subpath-test-dynamicpv-shq6" in namespace "provisioning-4894"
Sep 27 09:07:17.869: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-shq6" to be fully deleted
STEP: Deleting pod
Sep 27 09:07:20.346: INFO: Deleting pod "pod-subpath-test-dynamicpv-shq6" in namespace "provisioning-4894"
STEP: Deleting pvc
Sep 27 09:07:21.056: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comx2tgv"
... skipping 11 lines ...

• [SLOW TEST:62.979 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 182 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:07:12.679: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 27 09:07:13.866: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:07:13.866: INFO: Creating resource for dynamic PV
Sep 27 09:07:13.866: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7730fr4zj
STEP: creating a claim
Sep 27 09:07:14.108: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mmtg
STEP: Checking for subpath error in container status
Sep 27 09:07:31.305: INFO: Deleting pod "pod-subpath-test-dynamicpv-mmtg" in namespace "provisioning-7730"
Sep 27 09:07:31.543: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mmtg" to be fully deleted
STEP: Deleting pod
Sep 27 09:07:34.018: INFO: Deleting pod "pod-subpath-test-dynamicpv-mmtg" in namespace "provisioning-7730"
STEP: Deleting pvc
Sep 27 09:07:34.729: INFO: Deleting PersistentVolumeClaim "awskzv2l"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 09:07:51.642: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 54 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 113 lines ...
Sep 27 09:07:10.775: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-97329mzr2
STEP: creating a claim
Sep 27 09:07:11.021: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wffl
STEP: Creating a pod to test atomic-volume-subpath
Sep 27 09:07:11.760: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wffl" in namespace "provisioning-9732" to be "Succeeded or Failed"
Sep 27 09:07:12.005: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 244.972218ms
Sep 27 09:07:14.251: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490432673s
Sep 27 09:07:16.496: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.73601208s
Sep 27 09:07:18.744: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.983189492s
Sep 27 09:07:20.989: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 9.228985839s
Sep 27 09:07:23.235: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Pending", Reason="", readiness=false. Elapsed: 11.474458099s
... skipping 6 lines ...
Sep 27 09:07:38.963: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Running", Reason="", readiness=true. Elapsed: 27.202743049s
Sep 27 09:07:41.211: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Running", Reason="", readiness=true. Elapsed: 29.450537627s
Sep 27 09:07:43.458: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Running", Reason="", readiness=true. Elapsed: 31.697561363s
Sep 27 09:07:45.705: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Running", Reason="", readiness=true. Elapsed: 33.945009396s
Sep 27 09:07:47.952: INFO: Pod "pod-subpath-test-dynamicpv-wffl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.191387808s
STEP: Saw pod success
Sep 27 09:07:47.952: INFO: Pod "pod-subpath-test-dynamicpv-wffl" satisfied condition "Succeeded or Failed"
Sep 27 09:07:48.197: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-wffl container test-container-subpath-dynamicpv-wffl: <nil>
STEP: delete the pod
Sep 27 09:07:48.701: INFO: Waiting for pod pod-subpath-test-dynamicpv-wffl to disappear
Sep 27 09:07:48.947: INFO: Pod pod-subpath-test-dynamicpv-wffl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wffl
Sep 27 09:07:48.947: INFO: Deleting pod "pod-subpath-test-dynamicpv-wffl" in namespace "provisioning-9732"
... skipping 192 lines ...
Sep 27 09:06:59.416: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8759-e2e-scmwwch
STEP: creating a claim
Sep 27 09:06:59.663: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xjql
STEP: Creating a pod to test subpath
Sep 27 09:07:00.405: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xjql" in namespace "provisioning-8759" to be "Succeeded or Failed"
Sep 27 09:07:00.651: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 245.541486ms
Sep 27 09:07:02.898: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492906069s
Sep 27 09:07:05.146: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 4.74048649s
Sep 27 09:07:07.391: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986299171s
Sep 27 09:07:09.638: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 9.23300268s
Sep 27 09:07:11.888: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 11.482977354s
Sep 27 09:07:14.134: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 13.728786378s
Sep 27 09:07:16.381: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.975446264s
STEP: Saw pod success
Sep 27 09:07:16.381: INFO: Pod "pod-subpath-test-dynamicpv-xjql" satisfied condition "Succeeded or Failed"
Sep 27 09:07:16.626: INFO: Trying to get logs from node ip-172-20-51-172.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-xjql container test-container-subpath-dynamicpv-xjql: <nil>
STEP: delete the pod
Sep 27 09:07:17.128: INFO: Waiting for pod pod-subpath-test-dynamicpv-xjql to disappear
Sep 27 09:07:17.373: INFO: Pod pod-subpath-test-dynamicpv-xjql no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xjql
Sep 27 09:07:17.373: INFO: Deleting pod "pod-subpath-test-dynamicpv-xjql" in namespace "provisioning-8759"
STEP: Creating pod pod-subpath-test-dynamicpv-xjql
STEP: Creating a pod to test subpath
Sep 27 09:07:17.871: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xjql" in namespace "provisioning-8759" to be "Succeeded or Failed"
Sep 27 09:07:18.116: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 245.179937ms
Sep 27 09:07:20.363: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 2.49172967s
Sep 27 09:07:22.612: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 4.740328906s
Sep 27 09:07:24.858: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986717306s
Sep 27 09:07:27.104: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232520839s
Sep 27 09:07:29.350: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 11.478365595s
Sep 27 09:07:31.596: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 13.724425225s
Sep 27 09:07:33.842: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Pending", Reason="", readiness=false. Elapsed: 15.970990587s
Sep 27 09:07:36.089: INFO: Pod "pod-subpath-test-dynamicpv-xjql": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.217419254s
STEP: Saw pod success
Sep 27 09:07:36.089: INFO: Pod "pod-subpath-test-dynamicpv-xjql" satisfied condition "Succeeded or Failed"
Sep 27 09:07:36.334: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-xjql container test-container-subpath-dynamicpv-xjql: <nil>
STEP: delete the pod
Sep 27 09:07:36.830: INFO: Waiting for pod pod-subpath-test-dynamicpv-xjql to disappear
Sep 27 09:07:37.076: INFO: Pod pod-subpath-test-dynamicpv-xjql no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xjql
Sep 27 09:07:37.076: INFO: Deleting pod "pod-subpath-test-dynamicpv-xjql" in namespace "provisioning-8759"
... skipping 209 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 503 lines ...
Sep 27 09:07:39.159: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2502tgsf2
STEP: creating a claim
Sep 27 09:07:39.397: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2pg2
STEP: Creating a pod to test subpath
Sep 27 09:07:40.112: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2pg2" in namespace "provisioning-2502" to be "Succeeded or Failed"
Sep 27 09:07:40.350: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 237.415175ms
Sep 27 09:07:42.587: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.474748176s
Sep 27 09:07:44.826: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.713208436s
Sep 27 09:07:47.064: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.952073564s
Sep 27 09:07:49.302: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.189603157s
Sep 27 09:07:51.540: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.427441229s
Sep 27 09:07:53.777: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.66482428s
Sep 27 09:07:56.028: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.915491202s
Sep 27 09:07:58.266: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.153464568s
Sep 27 09:08:00.503: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.390782427s
Sep 27 09:08:02.743: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.630780412s
Sep 27 09:08:04.983: INFO: Pod "pod-subpath-test-dynamicpv-2pg2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.87012015s
STEP: Saw pod success
Sep 27 09:08:04.983: INFO: Pod "pod-subpath-test-dynamicpv-2pg2" satisfied condition "Succeeded or Failed"
Sep 27 09:08:05.220: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-2pg2 container test-container-subpath-dynamicpv-2pg2: <nil>
STEP: delete the pod
Sep 27 09:08:05.723: INFO: Waiting for pod pod-subpath-test-dynamicpv-2pg2 to disappear
Sep 27 09:08:05.967: INFO: Pod pod-subpath-test-dynamicpv-2pg2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2pg2
Sep 27 09:08:05.967: INFO: Deleting pod "pod-subpath-test-dynamicpv-2pg2" in namespace "provisioning-2502"
... skipping 463 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/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.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 116 lines ...
Sep 27 09:08:16.395: INFO: Waiting for pod aws-client to disappear
Sep 27 09:08:16.640: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 09:08:16.640: INFO: Deleting PersistentVolumeClaim "pvc-tc82q"
Sep 27 09:08:16.886: INFO: Deleting PersistentVolume "aws-j422m"
Sep 27 09:08:17.533: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0644fafc76d0d6c70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0644fafc76d0d6c70 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: ecb90b1f-3e43-4769-9fcd-4da2c4ec54cb
Sep 27 09:08:23.685: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0644fafc76d0d6c70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0644fafc76d0d6c70 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 888bda04-c48a-4182-a5af-c6fcd4ae2c14
Sep 27 09:08:29.845: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0644fafc76d0d6c70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0644fafc76d0d6c70 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 077767cd-9b68-4f13-8721-4378a534db55
Sep 27 09:08:35.970: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0644fafc76d0d6c70".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:08:35.971: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4350" for this suite.
... skipping 39 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 279 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:08:15.136: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 27 09:08:16.348: INFO: Creating resource for dynamic PV
Sep 27 09:08:16.348: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-152-e2e-scxsbtl
STEP: creating a claim
Sep 27 09:08:16.588: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dx5m
STEP: Checking for subpath error in container status
Sep 27 09:08:27.797: INFO: Deleting pod "pod-subpath-test-dynamicpv-dx5m" in namespace "provisioning-152"
Sep 27 09:08:28.041: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dx5m" to be fully deleted
STEP: Deleting pod
Sep 27 09:08:30.529: INFO: Deleting pod "pod-subpath-test-dynamicpv-dx5m" in namespace "provisioning-152"
STEP: Deleting pvc
Sep 27 09:08:31.250: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnps4q"
... skipping 11 lines ...

• [SLOW TEST:33.048 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 47 lines ...
STEP: Deleting pod aws-client in namespace volume-3507
Sep 27 09:08:34.177: INFO: Waiting for pod aws-client to disappear
Sep 27 09:08:34.417: INFO: Pod aws-client still exists
Sep 27 09:08:36.418: INFO: Waiting for pod aws-client to disappear
Sep 27 09:08:36.656: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 09:08:37.014: INFO: Couldn't delete PD "aws://ap-south-1a/vol-036216af707e1a6aa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-036216af707e1a6aa is currently attached to i-028544abdfa483e39
	status code: 400, request id: 49542942-0d3a-451d-83d2-f62f22597f91
Sep 27 09:08:43.152: INFO: Couldn't delete PD "aws://ap-south-1a/vol-036216af707e1a6aa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-036216af707e1a6aa is currently attached to i-028544abdfa483e39
	status code: 400, request id: 4010ae2e-d0e4-4d13-bbea-ea82c1f4bc30
Sep 27 09:08:49.292: INFO: Successfully deleted PD "aws://ap-south-1a/vol-036216af707e1a6aa".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:08:49.292: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3507" for this suite.
... skipping 182 lines ...
STEP: Deleting pod aws-client in namespace volume-7268
Sep 27 09:08:38.390: INFO: Waiting for pod aws-client to disappear
Sep 27 09:08:38.626: INFO: Pod aws-client still exists
Sep 27 09:08:40.627: INFO: Waiting for pod aws-client to disappear
Sep 27 09:08:40.863: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 09:08:42.018: INFO: Couldn't delete PD "aws://ap-south-1a/vol-052fea819266babfa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-052fea819266babfa is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: c791b090-d3df-47de-a5c7-77f75365a265
Sep 27 09:08:48.125: INFO: Couldn't delete PD "aws://ap-south-1a/vol-052fea819266babfa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-052fea819266babfa is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 72879d34-5b08-4dd8-85a2-67553746c7b4
Sep 27 09:08:54.273: INFO: Successfully deleted PD "aws://ap-south-1a/vol-052fea819266babfa".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:08:54.273: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7268" for this suite.
... skipping 256 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:08:58.623: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 09:09:00.093: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-south-1a]
Sep 27 09:09:00.094: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 201 lines ...
Sep 27 09:08:13.736: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4978nsqlw
STEP: creating a claim
Sep 27 09:08:13.982: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xt8c
STEP: Creating a pod to test subpath
Sep 27 09:08:14.722: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xt8c" in namespace "provisioning-4978" to be "Succeeded or Failed"
Sep 27 09:08:14.967: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 245.108347ms
Sep 27 09:08:17.214: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492212818s
Sep 27 09:08:19.460: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.738627832s
Sep 27 09:08:21.706: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.984815994s
Sep 27 09:08:23.954: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232135148s
Sep 27 09:08:26.204: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 11.481995055s
Sep 27 09:08:28.449: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 13.72761387s
Sep 27 09:08:30.696: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 15.974077832s
Sep 27 09:08:32.942: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.220408086s
STEP: Saw pod success
Sep 27 09:08:32.942: INFO: Pod "pod-subpath-test-dynamicpv-xt8c" satisfied condition "Succeeded or Failed"
Sep 27 09:08:33.187: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-xt8c container test-container-subpath-dynamicpv-xt8c: <nil>
STEP: delete the pod
Sep 27 09:08:33.691: INFO: Waiting for pod pod-subpath-test-dynamicpv-xt8c to disappear
Sep 27 09:08:33.936: INFO: Pod pod-subpath-test-dynamicpv-xt8c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xt8c
Sep 27 09:08:33.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-xt8c" in namespace "provisioning-4978"
STEP: Creating pod pod-subpath-test-dynamicpv-xt8c
STEP: Creating a pod to test subpath
Sep 27 09:08:34.440: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xt8c" in namespace "provisioning-4978" to be "Succeeded or Failed"
Sep 27 09:08:34.686: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 246.436032ms
Sep 27 09:08:36.936: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.496242547s
Sep 27 09:08:39.181: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.741912496s
Sep 27 09:08:41.428: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.988337592s
Sep 27 09:08:43.675: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Pending", Reason="", readiness=false. Elapsed: 9.235641149s
Sep 27 09:08:45.923: INFO: Pod "pod-subpath-test-dynamicpv-xt8c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.483318414s
STEP: Saw pod success
Sep 27 09:08:45.923: INFO: Pod "pod-subpath-test-dynamicpv-xt8c" satisfied condition "Succeeded or Failed"
Sep 27 09:08:46.172: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-xt8c container test-container-subpath-dynamicpv-xt8c: <nil>
STEP: delete the pod
Sep 27 09:08:46.679: INFO: Waiting for pod pod-subpath-test-dynamicpv-xt8c to disappear
Sep 27 09:08:46.924: INFO: Pod pod-subpath-test-dynamicpv-xt8c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xt8c
Sep 27 09:08:46.924: INFO: Deleting pod "pod-subpath-test-dynamicpv-xt8c" in namespace "provisioning-4978"
... skipping 535 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:08:17.972: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 27 09:08:19.146: INFO: Creating resource for dynamic PV
Sep 27 09:08:19.146: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4195-e2e-scsh2wz
STEP: creating a claim
Sep 27 09:08:19.381: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rc8s
STEP: Checking for subpath error in container status
Sep 27 09:08:44.557: INFO: Deleting pod "pod-subpath-test-dynamicpv-rc8s" in namespace "provisioning-4195"
Sep 27 09:08:44.792: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rc8s" to be fully deleted
STEP: Deleting pod
Sep 27 09:08:47.261: INFO: Deleting pod "pod-subpath-test-dynamicpv-rc8s" in namespace "provisioning-4195"
STEP: Deleting pvc
Sep 27 09:08:47.963: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcl24t"
... skipping 14 lines ...

• [SLOW TEST:62.586 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Sep 27 09:08:36.536: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1529qn95g
STEP: creating a claim
Sep 27 09:08:36.777: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vzsx
STEP: Creating a pod to test subpath
Sep 27 09:08:37.502: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vzsx" in namespace "provisioning-1529" to be "Succeeded or Failed"
Sep 27 09:08:37.743: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 240.992156ms
Sep 27 09:08:39.987: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.485325619s
Sep 27 09:08:42.229: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.726960187s
Sep 27 09:08:44.471: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.968862705s
Sep 27 09:08:46.712: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 9.209833527s
Sep 27 09:08:48.954: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 11.452133694s
Sep 27 09:08:51.196: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 13.693851715s
Sep 27 09:08:53.437: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.934968133s
Sep 27 09:08:55.679: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.177197657s
Sep 27 09:08:57.920: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.41813257s
Sep 27 09:09:00.162: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.660210101s
Sep 27 09:09:02.404: INFO: Pod "pod-subpath-test-dynamicpv-vzsx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.901736125s
STEP: Saw pod success
Sep 27 09:09:02.404: INFO: Pod "pod-subpath-test-dynamicpv-vzsx" satisfied condition "Succeeded or Failed"
Sep 27 09:09:02.645: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-vzsx container test-container-volume-dynamicpv-vzsx: <nil>
STEP: delete the pod
Sep 27 09:09:03.145: INFO: Waiting for pod pod-subpath-test-dynamicpv-vzsx to disappear
Sep 27 09:09:03.386: INFO: Pod pod-subpath-test-dynamicpv-vzsx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vzsx
Sep 27 09:09:03.386: INFO: Deleting pod "pod-subpath-test-dynamicpv-vzsx" in namespace "provisioning-1529"
... skipping 55 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:09:21.294: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 09:09:22.751: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-south-1a]
Sep 27 09:09:22.752: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 284 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:09:30.203: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 09:09:31.622: INFO: found topology map[topology.kubernetes.io/zone:ap-south-1a]
Sep 27 09:09:31.622: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:09:31.622: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 23 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:08:51.450: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:08:52.637: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 09:08:53.145: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-04af6327bbdb68f10".
Sep 27 09:08:53.145: INFO: Creating resource for pre-provisioned PV
Sep 27 09:08:53.145: INFO: Creating PVC and PV
... skipping 8 lines ...
Sep 27 09:09:05.132: INFO: PersistentVolumeClaim pvc-82zvm found but phase is Pending instead of Bound.
Sep 27 09:09:07.370: INFO: PersistentVolumeClaim pvc-82zvm found but phase is Pending instead of Bound.
Sep 27 09:09:09.611: INFO: PersistentVolumeClaim pvc-82zvm found and phase=Bound (15.918498597s)
Sep 27 09:09:09.611: INFO: Waiting up to 3m0s for PersistentVolume aws-v479q to have phase Bound
Sep 27 09:09:09.848: INFO: PersistentVolume aws-v479q found and phase=Bound (236.965114ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:09:11.036: INFO: Deleting pod "pod-7dfe56c5-9a00-4986-9453-5ce87a986c1a" in namespace "volumemode-6364"
Sep 27 09:09:11.277: INFO: Wait up to 5m0s for pod "pod-7dfe56c5-9a00-4986-9453-5ce87a986c1a" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 09:09:13.751: INFO: Deleting PersistentVolumeClaim "pvc-82zvm"
Sep 27 09:09:13.989: INFO: Deleting PersistentVolume "aws-v479q"
Sep 27 09:09:14.636: INFO: Couldn't delete PD "aws://ap-south-1a/vol-04af6327bbdb68f10", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04af6327bbdb68f10 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 77ceaccf-fb38-4110-964e-388a74868d07
Sep 27 09:09:20.803: INFO: Couldn't delete PD "aws://ap-south-1a/vol-04af6327bbdb68f10", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04af6327bbdb68f10 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: fb837e69-b759-437e-a811-f6890d88d436
Sep 27 09:09:26.926: INFO: Couldn't delete PD "aws://ap-south-1a/vol-04af6327bbdb68f10", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04af6327bbdb68f10 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: da2b7762-2274-4f8d-9580-6a3c910e1ad0
Sep 27 09:09:33.020: INFO: Successfully deleted PD "aws://ap-south-1a/vol-04af6327bbdb68f10".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:09:33.020: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6364" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:09:33.503: INFO: >>> kubeConfig: /root/.kube/config
... skipping 70 lines ...
Sep 27 09:08:23.510: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7664-e2e-scgp8h9
STEP: creating a claim
Sep 27 09:08:23.748: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5dqc
STEP: Creating a pod to test atomic-volume-subpath
Sep 27 09:08:24.465: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5dqc" in namespace "provisioning-7664" to be "Succeeded or Failed"
Sep 27 09:08:24.703: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 237.497504ms
Sep 27 09:08:26.941: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475283408s
Sep 27 09:08:29.188: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.722245276s
Sep 27 09:08:31.425: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.959829416s
Sep 27 09:08:33.663: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 9.197969926s
Sep 27 09:08:35.901: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Pending", Reason="", readiness=false. Elapsed: 11.435905199s
... skipping 8 lines ...
Sep 27 09:08:56.101: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Running", Reason="", readiness=true. Elapsed: 31.635740647s
Sep 27 09:08:58.350: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Running", Reason="", readiness=true. Elapsed: 33.884329692s
Sep 27 09:09:00.595: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Running", Reason="", readiness=true. Elapsed: 36.129449258s
Sep 27 09:09:02.841: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Running", Reason="", readiness=true. Elapsed: 38.375544577s
Sep 27 09:09:05.086: INFO: Pod "pod-subpath-test-dynamicpv-5dqc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.620604123s
STEP: Saw pod success
Sep 27 09:09:05.086: INFO: Pod "pod-subpath-test-dynamicpv-5dqc" satisfied condition "Succeeded or Failed"
Sep 27 09:09:05.337: INFO: Trying to get logs from node ip-172-20-63-190.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-5dqc container test-container-subpath-dynamicpv-5dqc: <nil>
STEP: delete the pod
Sep 27 09:09:05.857: INFO: Waiting for pod pod-subpath-test-dynamicpv-5dqc to disappear
Sep 27 09:09:06.101: INFO: Pod pod-subpath-test-dynamicpv-5dqc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5dqc
Sep 27 09:09:06.101: INFO: Deleting pod "pod-subpath-test-dynamicpv-5dqc" in namespace "provisioning-7664"
... skipping 35 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 84 lines ...
STEP: Deleting pod hostexec-ip-172-20-63-190.ap-south-1.compute.internal-9s4sz in namespace volumemode-4144
Sep 27 09:09:35.297: INFO: Deleting pod "pod-c565957f-550d-4d0c-b865-3bf8d8142065" in namespace "volumemode-4144"
Sep 27 09:09:35.539: INFO: Wait up to 5m0s for pod "pod-c565957f-550d-4d0c-b865-3bf8d8142065" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 09:09:38.024: INFO: Deleting PersistentVolumeClaim "pvc-pg65z"
Sep 27 09:09:38.269: INFO: Deleting PersistentVolume "aws-nmlf4"
Sep 27 09:09:38.879: INFO: Couldn't delete PD "aws://ap-south-1a/vol-008b55af1a3a79f85", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-008b55af1a3a79f85 is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 7e5e4138-d579-445d-b376-8b7a7afffebd
Sep 27 09:09:45.041: INFO: Successfully deleted PD "aws://ap-south-1a/vol-008b55af1a3a79f85".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:09:45.041: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4144" for this suite.
... skipping 74 lines ...
STEP: Deleting pod aws-client in namespace volume-137
Sep 27 09:09:33.531: INFO: Waiting for pod aws-client to disappear
Sep 27 09:09:33.771: INFO: Pod aws-client still exists
Sep 27 09:09:35.772: INFO: Waiting for pod aws-client to disappear
Sep 27 09:09:36.014: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 09:09:36.404: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0c3231ff0b7fb4632", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3231ff0b7fb4632 is currently attached to i-01936d56116684286
	status code: 400, request id: f8d7232f-71f0-4941-a6b2-440af00c84ea
Sep 27 09:09:42.542: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0c3231ff0b7fb4632", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3231ff0b7fb4632 is currently attached to i-01936d56116684286
	status code: 400, request id: fc3abd87-9318-4f92-9201-4f3517529204
Sep 27 09:09:48.651: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0c3231ff0b7fb4632".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:09:48.651: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-137" for this suite.
... skipping 143 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 76 lines ...
Sep 27 09:09:21.510: INFO: PersistentVolumeClaim pvc-7zkh9 found but phase is Pending instead of Bound.
Sep 27 09:09:23.752: INFO: PersistentVolumeClaim pvc-7zkh9 found and phase=Bound (11.455089999s)
Sep 27 09:09:23.752: INFO: Waiting up to 3m0s for PersistentVolume aws-w4ghb to have phase Bound
Sep 27 09:09:23.994: INFO: PersistentVolume aws-w4ghb found and phase=Bound (241.396558ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-2rj9
STEP: Creating a pod to test exec-volume-test
Sep 27 09:09:24.719: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-2rj9" in namespace "volume-8513" to be "Succeeded or Failed"
Sep 27 09:09:24.961: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 241.546478ms
Sep 27 09:09:27.204: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.484302677s
Sep 27 09:09:29.448: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.728243781s
Sep 27 09:09:31.690: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.970808184s
Sep 27 09:09:33.933: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 9.213426775s
Sep 27 09:09:36.176: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 11.45645369s
Sep 27 09:09:38.423: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.703906245s
Sep 27 09:09:40.665: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.945782584s
Sep 27 09:09:42.992: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Running", Reason="", readiness=true. Elapsed: 18.272146481s
Sep 27 09:09:45.234: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.514876713s
STEP: Saw pod success
Sep 27 09:09:45.234: INFO: Pod "exec-volume-test-preprovisionedpv-2rj9" satisfied condition "Succeeded or Failed"
Sep 27 09:09:45.476: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-2rj9 container exec-container-preprovisionedpv-2rj9: <nil>
STEP: delete the pod
Sep 27 09:09:46.134: INFO: Waiting for pod exec-volume-test-preprovisionedpv-2rj9 to disappear
Sep 27 09:09:46.375: INFO: Pod exec-volume-test-preprovisionedpv-2rj9 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-2rj9
Sep 27 09:09:46.375: INFO: Deleting pod "exec-volume-test-preprovisionedpv-2rj9" in namespace "volume-8513"
STEP: Deleting pv and pvc
Sep 27 09:09:46.619: INFO: Deleting PersistentVolumeClaim "pvc-7zkh9"
Sep 27 09:09:46.862: INFO: Deleting PersistentVolume "aws-w4ghb"
Sep 27 09:09:47.464: INFO: Couldn't delete PD "aws://ap-south-1a/vol-019e79b9248faf5e2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019e79b9248faf5e2 is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 47b2d443-d60c-42a7-9af0-60b5b082daae
Sep 27 09:09:53.596: INFO: Successfully deleted PD "aws://ap-south-1a/vol-019e79b9248faf5e2".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:09:53.596: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8513" for this suite.
... skipping 167 lines ...
Sep 27 09:09:23.205: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2895w557r
STEP: creating a claim
Sep 27 09:09:23.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-vm54
STEP: Creating a pod to test exec-volume-test
Sep 27 09:09:24.193: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vm54" in namespace "volume-2895" to be "Succeeded or Failed"
Sep 27 09:09:24.438: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 245.297669ms
Sep 27 09:09:26.685: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491850215s
Sep 27 09:09:28.932: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 4.739695887s
Sep 27 09:09:31.179: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986348413s
Sep 27 09:09:33.426: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 9.233245292s
Sep 27 09:09:35.672: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Pending", Reason="", readiness=false. Elapsed: 11.479647706s
Sep 27 09:09:37.921: INFO: Pod "exec-volume-test-dynamicpv-vm54": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.728330467s
STEP: Saw pod success
Sep 27 09:09:37.921: INFO: Pod "exec-volume-test-dynamicpv-vm54" satisfied condition "Succeeded or Failed"
Sep 27 09:09:38.172: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-vm54 container exec-container-dynamicpv-vm54: <nil>
STEP: delete the pod
Sep 27 09:09:38.681: INFO: Waiting for pod exec-volume-test-dynamicpv-vm54 to disappear
Sep 27 09:09:38.936: INFO: Pod exec-volume-test-dynamicpv-vm54 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vm54
Sep 27 09:09:38.936: INFO: Deleting pod "exec-volume-test-dynamicpv-vm54" in namespace "volume-2895"
... skipping 263 lines ...
Sep 27 09:09:24.688: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9535-e2e-sccfdjk
STEP: creating a claim
Sep 27 09:09:24.929: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wgtk
STEP: Creating a pod to test subpath
Sep 27 09:09:25.661: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wgtk" in namespace "provisioning-9535" to be "Succeeded or Failed"
Sep 27 09:09:25.902: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 240.767457ms
Sep 27 09:09:28.144: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.482409329s
Sep 27 09:09:30.385: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.723898742s
Sep 27 09:09:32.628: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.966728537s
Sep 27 09:09:34.869: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 9.208168473s
Sep 27 09:09:37.111: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 11.449811003s
Sep 27 09:09:39.352: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.690719899s
Sep 27 09:09:41.593: INFO: Pod "pod-subpath-test-dynamicpv-wgtk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.931948038s
STEP: Saw pod success
Sep 27 09:09:41.593: INFO: Pod "pod-subpath-test-dynamicpv-wgtk" satisfied condition "Succeeded or Failed"
Sep 27 09:09:41.834: INFO: Trying to get logs from node ip-172-20-51-172.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-wgtk container test-container-subpath-dynamicpv-wgtk: <nil>
STEP: delete the pod
Sep 27 09:09:42.338: INFO: Waiting for pod pod-subpath-test-dynamicpv-wgtk to disappear
Sep 27 09:09:42.579: INFO: Pod pod-subpath-test-dynamicpv-wgtk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wgtk
Sep 27 09:09:42.579: INFO: Deleting pod "pod-subpath-test-dynamicpv-wgtk" in namespace "provisioning-9535"
... skipping 129 lines ...
Sep 27 09:09:33.525: INFO: Creating resource for dynamic PV
Sep 27 09:09:33.525: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2143c6wlq
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 27 09:09:34.238: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 09:09:34.712: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:37.186: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:39.191: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:41.190: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:43.225: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:45.186: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:47.187: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:49.187: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:51.191: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:53.186: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:55.186: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:57.194: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:09:59.195: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:10:01.188: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:10:03.191: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:10:05.189: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2143c6wlq",
  	... // 3 identical fields
  }

Sep 27 09:10:05.663: INFO: Error updating pvc awsrmq4x: PersistentVolumeClaim "awsrmq4x" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 253 lines ...
Sep 27 09:09:42.758: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2611-e2e-scvdzfk
STEP: creating a claim
Sep 27 09:09:43.012: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l4fm
STEP: Creating a pod to test subpath
Sep 27 09:09:43.752: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l4fm" in namespace "provisioning-2611" to be "Succeeded or Failed"
Sep 27 09:09:43.997: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 244.953718ms
Sep 27 09:09:46.243: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490575992s
Sep 27 09:09:48.488: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.735966673s
Sep 27 09:09:50.734: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.981276643s
Sep 27 09:09:52.979: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 9.226932256s
Sep 27 09:09:55.227: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 11.474577147s
Sep 27 09:09:57.474: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Pending", Reason="", readiness=false. Elapsed: 13.721308808s
Sep 27 09:09:59.719: INFO: Pod "pod-subpath-test-dynamicpv-l4fm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.96657345s
STEP: Saw pod success
Sep 27 09:09:59.719: INFO: Pod "pod-subpath-test-dynamicpv-l4fm" satisfied condition "Succeeded or Failed"
Sep 27 09:09:59.964: INFO: Trying to get logs from node ip-172-20-63-190.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-l4fm container test-container-subpath-dynamicpv-l4fm: <nil>
STEP: delete the pod
Sep 27 09:10:00.469: INFO: Waiting for pod pod-subpath-test-dynamicpv-l4fm to disappear
Sep 27 09:10:00.713: INFO: Pod pod-subpath-test-dynamicpv-l4fm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l4fm
Sep 27 09:10:00.713: INFO: Deleting pod "pod-subpath-test-dynamicpv-l4fm" in namespace "provisioning-2611"
... skipping 252 lines ...
Sep 27 09:09:58.805: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-870958x9t
STEP: creating a claim
Sep 27 09:09:59.054: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4nbp
STEP: Creating a pod to test subpath
Sep 27 09:09:59.803: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4nbp" in namespace "provisioning-8709" to be "Succeeded or Failed"
Sep 27 09:10:00.050: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 247.74049ms
Sep 27 09:10:02.299: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.496145904s
Sep 27 09:10:04.548: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.744764518s
Sep 27 09:10:06.796: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.992986403s
Sep 27 09:10:09.047: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.243896879s
Sep 27 09:10:11.296: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.493107874s
Sep 27 09:10:13.544: INFO: Pod "pod-subpath-test-dynamicpv-4nbp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.741385535s
STEP: Saw pod success
Sep 27 09:10:13.544: INFO: Pod "pod-subpath-test-dynamicpv-4nbp" satisfied condition "Succeeded or Failed"
Sep 27 09:10:13.792: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-4nbp container test-container-subpath-dynamicpv-4nbp: <nil>
STEP: delete the pod
Sep 27 09:10:14.298: INFO: Waiting for pod pod-subpath-test-dynamicpv-4nbp to disappear
Sep 27 09:10:14.546: INFO: Pod pod-subpath-test-dynamicpv-4nbp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4nbp
Sep 27 09:10:14.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-4nbp" in namespace "provisioning-8709"
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:09:57.942: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 27 09:09:59.172: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:09:59.172: INFO: Creating resource for dynamic PV
Sep 27 09:09:59.172: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4394w5wsd
STEP: creating a claim
Sep 27 09:09:59.418: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s7xt
STEP: Checking for subpath error in container status
Sep 27 09:10:18.651: INFO: Deleting pod "pod-subpath-test-dynamicpv-s7xt" in namespace "provisioning-4394"
Sep 27 09:10:18.902: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-s7xt" to be fully deleted
STEP: Deleting pod
Sep 27 09:10:21.400: INFO: Deleting pod "pod-subpath-test-dynamicpv-s7xt" in namespace "provisioning-4394"
STEP: Deleting pvc
Sep 27 09:10:22.135: INFO: Deleting PersistentVolumeClaim "awshs2fb"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 310 lines ...
Sep 27 09:09:32.054: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1414-e2e-scs8r57      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-1414    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-1414-e2e-scs8r57,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1414    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-1414-e2e-scs8r57,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1414    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-1414-e2e-scs8r57,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1414-e2e-scs8r57    dcb2f976-aa8c-4be1-af46-cc9f0c7fb2ed 9704 0 2021-09-27 09:09:32 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-27 09:09:32 +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-tx5fm pvc- provisioning-1414  c25aa1d4-0867-47fa-b767-79d61fab70a6 9722 0 2021-09-27 09:09:33 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-27 09:09:33 +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-1414-e2e-scs8r57,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-89760348-559b-4a4f-8c6b-bbf59e6815ed in namespace provisioning-1414
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 27 09:09:50.684: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-sql54" in namespace "provisioning-1414" to be "Succeeded or Failed"
Sep 27 09:09:50.921: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 237.412921ms
Sep 27 09:09:53.160: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476427836s
Sep 27 09:09:55.398: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 4.714137533s
Sep 27 09:09:57.636: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 6.951836372s
Sep 27 09:09:59.873: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 9.189591801s
Sep 27 09:10:02.115: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 11.43089217s
... skipping 5 lines ...
Sep 27 09:10:15.551: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 24.866639986s
Sep 27 09:10:17.789: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 27.105276688s
Sep 27 09:10:20.031: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 29.346966243s
Sep 27 09:10:22.269: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Pending", Reason="", readiness=false. Elapsed: 31.584817511s
Sep 27 09:10:24.507: INFO: Pod "pvc-volume-tester-writer-sql54": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.822727789s
STEP: Saw pod success
Sep 27 09:10:24.507: INFO: Pod "pvc-volume-tester-writer-sql54" satisfied condition "Succeeded or Failed"
Sep 27 09:10:24.984: INFO: Pod pvc-volume-tester-writer-sql54 has the following logs: 
Sep 27 09:10:24.984: INFO: Deleting pod "pvc-volume-tester-writer-sql54" in namespace "provisioning-1414"
Sep 27 09:10:25.228: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-sql54" 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-51-172.ap-south-1.compute.internal"
Sep 27 09:10:26.188: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-brp4r" in namespace "provisioning-1414" to be "Succeeded or Failed"
Sep 27 09:10:26.426: INFO: Pod "pvc-volume-tester-reader-brp4r": Phase="Pending", Reason="", readiness=false. Elapsed: 237.959291ms
Sep 27 09:10:28.664: INFO: Pod "pvc-volume-tester-reader-brp4r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475985017s
Sep 27 09:10:30.902: INFO: Pod "pvc-volume-tester-reader-brp4r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.713916268s
Sep 27 09:10:33.140: INFO: Pod "pvc-volume-tester-reader-brp4r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.951805859s
Sep 27 09:10:35.378: INFO: Pod "pvc-volume-tester-reader-brp4r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 9.189450539s
STEP: Saw pod success
Sep 27 09:10:35.378: INFO: Pod "pvc-volume-tester-reader-brp4r" satisfied condition "Succeeded or Failed"
Sep 27 09:10:35.854: INFO: Pod pvc-volume-tester-reader-brp4r has the following logs: hello world

Sep 27 09:10:35.854: INFO: Deleting pod "pvc-volume-tester-reader-brp4r" in namespace "provisioning-1414"
Sep 27 09:10:36.099: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-brp4r" to be fully deleted
Sep 27 09:10:36.337: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-tx5fm] to have phase Bound
Sep 27 09:10:36.574: INFO: PersistentVolumeClaim pvc-tx5fm found and phase=Bound (237.474156ms)
... skipping 109 lines ...

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


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 248 lines ...
Sep 27 09:10:22.709: INFO: PersistentVolumeClaim pvc-vsq4t found but phase is Pending instead of Bound.
Sep 27 09:10:24.947: INFO: PersistentVolumeClaim pvc-vsq4t found and phase=Bound (6.948833425s)
Sep 27 09:10:24.947: INFO: Waiting up to 3m0s for PersistentVolume aws-zzc6h to have phase Bound
Sep 27 09:10:25.184: INFO: PersistentVolume aws-zzc6h found and phase=Bound (236.794443ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-s2d8
STEP: Creating a pod to test exec-volume-test
Sep 27 09:10:25.898: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-s2d8" in namespace "volume-4875" to be "Succeeded or Failed"
Sep 27 09:10:26.137: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 239.304963ms
Sep 27 09:10:28.374: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476424679s
Sep 27 09:10:30.612: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.714014181s
Sep 27 09:10:32.851: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.953062055s
Sep 27 09:10:35.089: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 9.190558097s
Sep 27 09:10:37.327: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 11.428570953s
Sep 27 09:10:39.564: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.66605787s
Sep 27 09:10:41.801: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.90327268s
Sep 27 09:10:44.044: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.145759309s
STEP: Saw pod success
Sep 27 09:10:44.044: INFO: Pod "exec-volume-test-preprovisionedpv-s2d8" satisfied condition "Succeeded or Failed"
Sep 27 09:10:44.284: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-s2d8 container exec-container-preprovisionedpv-s2d8: <nil>
STEP: delete the pod
Sep 27 09:10:44.774: INFO: Waiting for pod exec-volume-test-preprovisionedpv-s2d8 to disappear
Sep 27 09:10:45.010: INFO: Pod exec-volume-test-preprovisionedpv-s2d8 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-s2d8
Sep 27 09:10:45.010: INFO: Deleting pod "exec-volume-test-preprovisionedpv-s2d8" in namespace "volume-4875"
STEP: Deleting pv and pvc
Sep 27 09:10:45.247: INFO: Deleting PersistentVolumeClaim "pvc-vsq4t"
Sep 27 09:10:45.486: INFO: Deleting PersistentVolume "aws-zzc6h"
Sep 27 09:10:46.109: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0c2e3b7e65908c813", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c2e3b7e65908c813 is currently attached to i-028544abdfa483e39
	status code: 400, request id: d8c0f9c4-5345-444e-b09a-05b0d3a5f9b4
Sep 27 09:10:52.192: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0c2e3b7e65908c813", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c2e3b7e65908c813 is currently attached to i-028544abdfa483e39
	status code: 400, request id: dd2891a4-fcce-4c8f-ba57-e8ef2fdc1864
Sep 27 09:10:58.364: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0c2e3b7e65908c813", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c2e3b7e65908c813 is currently attached to i-028544abdfa483e39
	status code: 400, request id: b2a1e755-ea7a-4267-b278-fb212e2ed4f8
Sep 27 09:11:04.485: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0c2e3b7e65908c813".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:11:04.486: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4875" for this suite.
... skipping 384 lines ...
Sep 27 09:10:19.896: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 09:10:21.121: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-05042ee295e89e9dc".
Sep 27 09:10:21.121: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-4p8j
STEP: Creating a pod to test exec-volume-test
Sep 27 09:10:21.375: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-4p8j" in namespace "volume-3234" to be "Succeeded or Failed"
Sep 27 09:10:21.620: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 245.034368ms
Sep 27 09:10:23.866: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490493857s
Sep 27 09:10:26.113: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.737503938s
Sep 27 09:10:28.360: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.984142969s
Sep 27 09:10:30.605: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 9.229962013s
Sep 27 09:10:32.852: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 11.476064016s
Sep 27 09:10:35.098: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 13.722548946s
Sep 27 09:10:37.345: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Pending", Reason="", readiness=false. Elapsed: 15.969176377s
Sep 27 09:10:39.590: INFO: Pod "exec-volume-test-inlinevolume-4p8j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.21484889s
STEP: Saw pod success
Sep 27 09:10:39.590: INFO: Pod "exec-volume-test-inlinevolume-4p8j" satisfied condition "Succeeded or Failed"
Sep 27 09:10:39.836: INFO: Trying to get logs from node ip-172-20-63-190.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-4p8j container exec-container-inlinevolume-4p8j: <nil>
STEP: delete the pod
Sep 27 09:10:40.336: INFO: Waiting for pod exec-volume-test-inlinevolume-4p8j to disappear
Sep 27 09:10:40.583: INFO: Pod exec-volume-test-inlinevolume-4p8j no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-4p8j
Sep 27 09:10:40.583: INFO: Deleting pod "exec-volume-test-inlinevolume-4p8j" in namespace "volume-3234"
Sep 27 09:10:41.217: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: fd498120-9b79-4564-9dd4-651d06179c31
Sep 27 09:10:47.418: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: eb7deefb-e336-466d-be12-60e7857c291f
Sep 27 09:10:53.554: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: a97b7248-c5ee-4b49-be8c-191694e13b6b
Sep 27 09:10:59.653: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 80c58e60-63fa-4f7e-a2b0-6c21a062dfdb
Sep 27 09:11:06.215: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: 612cc70f-86ae-4a2a-9082-a65a363c03b0
Sep 27 09:11:12.381: INFO: Couldn't delete PD "aws://ap-south-1a/vol-05042ee295e89e9dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05042ee295e89e9dc is currently attached to i-01f7a911a4abc3efb
	status code: 400, request id: a7fa9532-1dca-4209-bf3c-62ef566e94f4
Sep 27 09:11:18.489: INFO: Successfully deleted PD "aws://ap-south-1a/vol-05042ee295e89e9dc".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:11:18.489: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3234" for this suite.
... skipping 133 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 439 lines ...
Sep 27 09:11:34.924: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:10:39.124: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:10:40.354: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 09:10:41.575: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-07d8fa3ec900621dd".
Sep 27 09:10:41.575: INFO: Creating resource for pre-provisioned PV
Sep 27 09:10:41.575: INFO: Creating PVC and PV
... skipping 6 lines ...
Sep 27 09:10:49.121: INFO: PersistentVolumeClaim pvc-t4vlb found but phase is Pending instead of Bound.
Sep 27 09:10:51.369: INFO: PersistentVolumeClaim pvc-t4vlb found but phase is Pending instead of Bound.
Sep 27 09:10:53.614: INFO: PersistentVolumeClaim pvc-t4vlb found and phase=Bound (11.481822563s)
Sep 27 09:10:53.614: INFO: Waiting up to 3m0s for PersistentVolume aws-9xpnv to have phase Bound
Sep 27 09:10:53.859: INFO: PersistentVolume aws-9xpnv found and phase=Bound (244.792652ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:10:57.349: INFO: Deleting pod "pod-0d609bcb-26ca-4159-a099-083aafb81f54" in namespace "volumemode-658"
Sep 27 09:10:57.596: INFO: Wait up to 5m0s for pod "pod-0d609bcb-26ca-4159-a099-083aafb81f54" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 09:10:57.844: INFO: Deleting PersistentVolumeClaim "pvc-t4vlb"
Sep 27 09:10:58.090: INFO: Deleting PersistentVolume "aws-9xpnv"
Sep 27 09:10:58.958: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: c35612db-02f1-41ed-9b9d-f064eecea9ba
Sep 27 09:11:05.074: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 7c0ba7eb-3c04-490e-a131-907f8f1f5952
Sep 27 09:11:11.172: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: 78f2248f-885d-468e-9bc8-fad3ae2c2ee4
Sep 27 09:11:17.284: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: c55c35de-6191-4d02-bb80-b1d64b7726bd
Sep 27 09:11:23.389: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: f549f2dd-2fa9-4457-9adb-ee6ed5367fc5
Sep 27 09:11:29.522: INFO: Couldn't delete PD "aws://ap-south-1a/vol-07d8fa3ec900621dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07d8fa3ec900621dd is currently attached to i-0cc087a536689f4bd
	status code: 400, request id: a58fb15a-ee39-4579-9cfa-8f6742dd0d73
Sep 27 09:11:35.657: INFO: Successfully deleted PD "aws://ap-south-1a/vol-07d8fa3ec900621dd".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:11:35.657: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-658" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Volume FStype [Feature:vsphere]
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:11:34.929: INFO: >>> kubeConfig: /root/.kube/config
... skipping 143 lines ...
Sep 27 09:10:02.899: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1222sg8kn      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-1222    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-1222sg8kn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1222    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-1222sg8kn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1222    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-1222sg8kn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1222sg8kn    9276db9c-3cfd-4f30-b19d-d3465e8f96ef 10618 0 2021-09-27 09:10:03 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-27 09:10:03 +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-lzfct pvc- provisioning-1222  790465fb-86ce-4c5f-8b52-7836bfdca31f 10635 0 2021-09-27 09:10:04 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-27 09:10:04 +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-1222sg8kn,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-8a46c7e9-922e-40c1-a1a0-b7fbd0c9c0ae in namespace provisioning-1222
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 27 09:10:17.611: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-v6cgj" in namespace "provisioning-1222" to be "Succeeded or Failed"
Sep 27 09:10:17.857: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 245.783303ms
Sep 27 09:10:20.104: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492854102s
Sep 27 09:10:22.352: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.740457967s
Sep 27 09:10:24.598: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986464846s
Sep 27 09:10:26.844: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 9.233165253s
Sep 27 09:10:29.091: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.480047513s
... skipping 7 lines ...
Sep 27 09:10:47.063: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 29.452040285s
Sep 27 09:10:49.318: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 31.70648621s
Sep 27 09:10:51.563: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 33.952240206s
Sep 27 09:10:53.809: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Pending", Reason="", readiness=false. Elapsed: 36.198030026s
Sep 27 09:10:56.057: INFO: Pod "pvc-volume-tester-writer-v6cgj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.446031049s
STEP: Saw pod success
Sep 27 09:10:56.057: INFO: Pod "pvc-volume-tester-writer-v6cgj" satisfied condition "Succeeded or Failed"
Sep 27 09:10:56.587: INFO: Pod pvc-volume-tester-writer-v6cgj has the following logs: 
Sep 27 09:10:56.587: INFO: Deleting pod "pvc-volume-tester-writer-v6cgj" in namespace "provisioning-1222"
Sep 27 09:10:56.844: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-v6cgj" 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-46-234.ap-south-1.compute.internal"
Sep 27 09:10:57.833: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-d5775" in namespace "provisioning-1222" to be "Succeeded or Failed"
Sep 27 09:10:58.078: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Pending", Reason="", readiness=false. Elapsed: 245.512118ms
Sep 27 09:11:00.325: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492393456s
Sep 27 09:11:02.571: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Pending", Reason="", readiness=false. Elapsed: 4.738633137s
Sep 27 09:11:04.817: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Pending", Reason="", readiness=false. Elapsed: 6.984542368s
Sep 27 09:11:07.065: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232711645s
Sep 27 09:11:09.312: INFO: Pod "pvc-volume-tester-reader-d5775": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.47937422s
STEP: Saw pod success
Sep 27 09:11:09.312: INFO: Pod "pvc-volume-tester-reader-d5775" satisfied condition "Succeeded or Failed"
Sep 27 09:11:09.804: INFO: Pod pvc-volume-tester-reader-d5775 has the following logs: hello world

Sep 27 09:11:09.804: INFO: Deleting pod "pvc-volume-tester-reader-d5775" in namespace "provisioning-1222"
Sep 27 09:11:10.070: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-d5775" to be fully deleted
Sep 27 09:11:10.316: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lzfct] to have phase Bound
Sep 27 09:11:10.561: INFO: PersistentVolumeClaim pvc-lzfct found and phase=Bound (245.355239ms)
... skipping 208 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:10:31.738: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 09:10:32.943: INFO: Creating resource for dynamic PV
Sep 27 09:10:32.943: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4961-e2e-scn5n6g
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 09:10:38.636: INFO: Deleting pod "pod-df2510eb-b20d-483c-a319-4b8c2e209c95" in namespace "volumemode-4961"
Sep 27 09:10:38.882: INFO: Wait up to 5m0s for pod "pod-df2510eb-b20d-483c-a319-4b8c2e209c95" to be fully deleted
STEP: Deleting pvc
Sep 27 09:10:41.846: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxv5pq"
Sep 27 09:10:42.089: INFO: Waiting up to 5m0s for PersistentVolume pvc-6324c41f-f403-4d72-af85-29284b213f8f to get deleted
Sep 27 09:10:42.330: INFO: PersistentVolume pvc-6324c41f-f403-4d72-af85-29284b213f8f found and phase=Released (240.220783ms)
... skipping 19 lines ...

• [SLOW TEST:79.469 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.ITP296yt1/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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 09:11:51.209: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 286 lines ...
Sep 27 09:11:19.640: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5087c6jwr
STEP: creating a claim
Sep 27 09:11:19.883: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-hzg8
STEP: Creating a pod to test exec-volume-test
Sep 27 09:11:20.614: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-hzg8" in namespace "volume-5087" to be "Succeeded or Failed"
Sep 27 09:11:20.856: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 241.572198ms
Sep 27 09:11:23.098: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.483529947s
Sep 27 09:11:25.340: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.725521403s
Sep 27 09:11:27.582: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.967589905s
Sep 27 09:11:29.825: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 9.210545372s
Sep 27 09:11:32.067: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 11.452484801s
Sep 27 09:11:34.310: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.69541673s
Sep 27 09:11:36.554: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.939171184s
Sep 27 09:11:38.796: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 18.182046854s
Sep 27 09:11:41.039: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Pending", Reason="", readiness=false. Elapsed: 20.424852839s
Sep 27 09:11:43.281: INFO: Pod "exec-volume-test-dynamicpv-hzg8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.666823082s
STEP: Saw pod success
Sep 27 09:11:43.281: INFO: Pod "exec-volume-test-dynamicpv-hzg8" satisfied condition "Succeeded or Failed"
Sep 27 09:11:43.526: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-hzg8 container exec-container-dynamicpv-hzg8: <nil>
STEP: delete the pod
Sep 27 09:11:44.021: INFO: Waiting for pod exec-volume-test-dynamicpv-hzg8 to disappear
Sep 27 09:11:44.262: INFO: Pod exec-volume-test-dynamicpv-hzg8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-hzg8
Sep 27 09:11:44.262: INFO: Deleting pod "exec-volume-test-dynamicpv-hzg8" in namespace "volume-5087"
... skipping 417 lines ...
Sep 27 09:11:32.346: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4168-e2e-scqwhm6
STEP: creating a claim
Sep 27 09:11:32.587: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 27 09:11:33.071: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 09:11:33.553: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:36.037: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:38.037: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:40.037: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:42.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:44.036: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:46.036: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:48.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:50.038: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:52.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:54.040: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:56.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:11:58.038: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:12:00.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:12:02.035: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

Sep 27 09:12:04.037: INFO: Error updating pvc ebs.csi.aws.combpzww: PersistentVolumeClaim "ebs.csi.aws.combpzww" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4168-e2e-scqwhm6",
  	... // 3 identical fields
  }

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 368 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:10:39.026: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 27 09:10:40.231: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:10:40.231: INFO: Creating resource for dynamic PV
Sep 27 09:10:40.232: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7361p45hz
STEP: creating a claim
Sep 27 09:10:40.473: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pztz
STEP: Checking for subpath error in container status
Sep 27 09:11:51.687: INFO: Deleting pod "pod-subpath-test-dynamicpv-pztz" in namespace "provisioning-7361"
Sep 27 09:11:51.932: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pztz" to be fully deleted
STEP: Deleting pod
Sep 27 09:11:54.415: INFO: Deleting pod "pod-subpath-test-dynamicpv-pztz" in namespace "provisioning-7361"
STEP: Deleting pvc
Sep 27 09:11:55.140: INFO: Deleting PersistentVolumeClaim "awsxx2b2"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 36 lines ...
STEP: Deleting pod hostexec-ip-172-20-57-163.ap-south-1.compute.internal-t6h7d in namespace volumemode-4495
Sep 27 09:12:07.464: INFO: Deleting pod "pod-a8725d17-2076-4f1f-9884-54218d9e8038" in namespace "volumemode-4495"
Sep 27 09:12:07.712: INFO: Wait up to 5m0s for pod "pod-a8725d17-2076-4f1f-9884-54218d9e8038" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 09:12:10.204: INFO: Deleting PersistentVolumeClaim "pvc-wj542"
Sep 27 09:12:10.449: INFO: Deleting PersistentVolume "aws-z5kxg"
Sep 27 09:12:11.326: INFO: Couldn't delete PD "aws://ap-south-1a/vol-09a14f80f0976b59f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09a14f80f0976b59f is currently attached to i-028544abdfa483e39
	status code: 400, request id: f4a3f3e7-61f2-4b3d-8af6-0668e0c0f4b9
Sep 27 09:12:17.416: INFO: Successfully deleted PD "aws://ap-south-1a/vol-09a14f80f0976b59f".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:12:17.416: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4495" for this suite.
... skipping 24 lines ...
Sep 27 09:11:47.361: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-96464dt8w
STEP: creating a claim
Sep 27 09:11:47.599: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 27 09:11:48.074: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 09:11:48.550: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:11:51.025: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:11:53.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:11:55.024: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:11:57.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:11:59.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:01.025: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:03.027: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:05.029: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:07.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:09.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:11.027: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:13.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:15.029: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:17.026: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:19.073: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96464dt8w",
  	... // 3 identical fields
  }

Sep 27 09:12:19.548: INFO: Error updating pvc aws9r6fg: PersistentVolumeClaim "aws9r6fg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 41 lines ...
Sep 27 09:11:58.004: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7781-e2e-scm9dbg
STEP: creating a claim
Sep 27 09:11:58.242: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jx9q
STEP: Creating a pod to test exec-volume-test
Sep 27 09:11:58.985: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jx9q" in namespace "volume-7781" to be "Succeeded or Failed"
Sep 27 09:11:59.222: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 237.713663ms
Sep 27 09:12:01.462: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.477754492s
Sep 27 09:12:03.701: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.716719869s
Sep 27 09:12:05.939: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.954845786s
Sep 27 09:12:08.178: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 9.193130868s
Sep 27 09:12:10.417: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Pending", Reason="", readiness=false. Elapsed: 11.43209022s
Sep 27 09:12:12.657: INFO: Pod "exec-volume-test-dynamicpv-jx9q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.672833128s
STEP: Saw pod success
Sep 27 09:12:12.657: INFO: Pod "exec-volume-test-dynamicpv-jx9q" satisfied condition "Succeeded or Failed"
Sep 27 09:12:12.895: INFO: Trying to get logs from node ip-172-20-51-172.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-jx9q container exec-container-dynamicpv-jx9q: <nil>
STEP: delete the pod
Sep 27 09:12:13.378: INFO: Waiting for pod exec-volume-test-dynamicpv-jx9q to disappear
Sep 27 09:12:13.616: INFO: Pod exec-volume-test-dynamicpv-jx9q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jx9q
Sep 27 09:12:13.616: INFO: Deleting pod "exec-volume-test-dynamicpv-jx9q" in namespace "volume-7781"
... skipping 125 lines ...
Sep 27 09:12:13.240: INFO: Waiting for pod aws-client to disappear
Sep 27 09:12:13.480: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 09:12:13.480: INFO: Deleting PersistentVolumeClaim "pvc-f9lhn"
Sep 27 09:12:13.721: INFO: Deleting PersistentVolume "aws-phzqt"
Sep 27 09:12:15.070: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0452a1b30a19ad4e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0452a1b30a19ad4e3 is currently attached to i-028544abdfa483e39
	status code: 400, request id: 7a7c1038-0a79-4408-a340-c156d84a7648
Sep 27 09:12:21.168: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0452a1b30a19ad4e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0452a1b30a19ad4e3 is currently attached to i-028544abdfa483e39
	status code: 400, request id: 08901965-aba0-4051-b906-21f2eff4317a
Sep 27 09:12:27.320: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0452a1b30a19ad4e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0452a1b30a19ad4e3 is currently attached to i-028544abdfa483e39
	status code: 400, request id: 2c2f8af7-8de2-4a77-bf40-2a63ca06d44e
Sep 27 09:12:33.428: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0452a1b30a19ad4e3".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:12:33.428: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8003" for this suite.
... skipping 104 lines ...
Sep 27 09:12:07.951: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3474-e2e-scvslzs
STEP: creating a claim
Sep 27 09:12:08.188: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-hwrh
STEP: Creating a pod to test exec-volume-test
Sep 27 09:12:08.915: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-hwrh" in namespace "volume-3474" to be "Succeeded or Failed"
Sep 27 09:12:09.152: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Pending", Reason="", readiness=false. Elapsed: 236.479707ms
Sep 27 09:12:11.390: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475218903s
Sep 27 09:12:13.627: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.712327432s
Sep 27 09:12:15.864: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.948849647s
Sep 27 09:12:18.102: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Pending", Reason="", readiness=false. Elapsed: 9.187447939s
Sep 27 09:12:20.341: INFO: Pod "exec-volume-test-dynamicpv-hwrh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.425787109s
STEP: Saw pod success
Sep 27 09:12:20.341: INFO: Pod "exec-volume-test-dynamicpv-hwrh" satisfied condition "Succeeded or Failed"
Sep 27 09:12:20.592: INFO: Trying to get logs from node ip-172-20-63-190.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-hwrh container exec-container-dynamicpv-hwrh: <nil>
STEP: delete the pod
Sep 27 09:12:21.078: INFO: Waiting for pod exec-volume-test-dynamicpv-hwrh to disappear
Sep 27 09:12:21.316: INFO: Pod exec-volume-test-dynamicpv-hwrh no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-hwrh
Sep 27 09:12:21.316: INFO: Deleting pod "exec-volume-test-dynamicpv-hwrh" in namespace "volume-3474"
... skipping 34 lines ...
Sep 27 09:12:03.258: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5465dtpn9
STEP: creating a claim
Sep 27 09:12:03.504: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ttkw
STEP: Creating a pod to test multi_subpath
Sep 27 09:12:04.248: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ttkw" in namespace "provisioning-5465" to be "Succeeded or Failed"
Sep 27 09:12:04.493: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 245.130723ms
Sep 27 09:12:06.741: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.493373552s
Sep 27 09:12:08.988: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.740350238s
Sep 27 09:12:11.235: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986564373s
Sep 27 09:12:13.480: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232092497s
Sep 27 09:12:15.726: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.478112139s
Sep 27 09:12:17.972: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.72361931s
Sep 27 09:12:20.217: INFO: Pod "pod-subpath-test-dynamicpv-ttkw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.969308657s
STEP: Saw pod success
Sep 27 09:12:20.217: INFO: Pod "pod-subpath-test-dynamicpv-ttkw" satisfied condition "Succeeded or Failed"
Sep 27 09:12:20.462: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-ttkw container test-container-subpath-dynamicpv-ttkw: <nil>
STEP: delete the pod
Sep 27 09:12:20.967: INFO: Waiting for pod pod-subpath-test-dynamicpv-ttkw to disappear
Sep 27 09:12:21.212: INFO: Pod pod-subpath-test-dynamicpv-ttkw no longer exists
STEP: Deleting pod
Sep 27 09:12:21.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-ttkw" in namespace "provisioning-5465"
... skipping 47 lines ...
Sep 27 09:12:07.799: INFO: PersistentVolumeClaim pvc-7mxqp found but phase is Pending instead of Bound.
Sep 27 09:12:10.046: INFO: PersistentVolumeClaim pvc-7mxqp found and phase=Bound (11.482958948s)
Sep 27 09:12:10.046: INFO: Waiting up to 3m0s for PersistentVolume aws-kblf2 to have phase Bound
Sep 27 09:12:10.292: INFO: PersistentVolume aws-kblf2 found and phase=Bound (246.628172ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-k9cv
STEP: Creating a pod to test exec-volume-test
Sep 27 09:12:11.030: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-k9cv" in namespace "volume-5293" to be "Succeeded or Failed"
Sep 27 09:12:11.281: INFO: Pod "exec-volume-test-preprovisionedpv-k9cv": Phase="Pending", Reason="", readiness=false. Elapsed: 250.605109ms
Sep 27 09:12:13.528: INFO: Pod "exec-volume-test-preprovisionedpv-k9cv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.497273387s
Sep 27 09:12:15.782: INFO: Pod "exec-volume-test-preprovisionedpv-k9cv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.751818074s
Sep 27 09:12:18.028: INFO: Pod "exec-volume-test-preprovisionedpv-k9cv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.997608582s
STEP: Saw pod success
Sep 27 09:12:18.028: INFO: Pod "exec-volume-test-preprovisionedpv-k9cv" satisfied condition "Succeeded or Failed"
Sep 27 09:12:18.273: INFO: Trying to get logs from node ip-172-20-57-163.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-k9cv container exec-container-preprovisionedpv-k9cv: <nil>
STEP: delete the pod
Sep 27 09:12:18.787: INFO: Waiting for pod exec-volume-test-preprovisionedpv-k9cv to disappear
Sep 27 09:12:19.068: INFO: Pod exec-volume-test-preprovisionedpv-k9cv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-k9cv
Sep 27 09:12:19.068: INFO: Deleting pod "exec-volume-test-preprovisionedpv-k9cv" in namespace "volume-5293"
STEP: Deleting pv and pvc
Sep 27 09:12:19.314: INFO: Deleting PersistentVolumeClaim "pvc-7mxqp"
Sep 27 09:12:19.562: INFO: Deleting PersistentVolume "aws-kblf2"
Sep 27 09:12:20.159: INFO: Couldn't delete PD "aws://ap-south-1a/vol-08120ecd7cf4169f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08120ecd7cf4169f0 is currently attached to i-028544abdfa483e39
	status code: 400, request id: 2163cd40-9cac-4ea2-85e4-4d001ae2a590
Sep 27 09:12:26.271: INFO: Couldn't delete PD "aws://ap-south-1a/vol-08120ecd7cf4169f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08120ecd7cf4169f0 is currently attached to i-028544abdfa483e39
	status code: 400, request id: ba93e947-174e-456d-aec9-14dd6ca36829
Sep 27 09:12:32.412: INFO: Couldn't delete PD "aws://ap-south-1a/vol-08120ecd7cf4169f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08120ecd7cf4169f0 is currently attached to i-028544abdfa483e39
	status code: 400, request id: f0778313-8968-4964-b1f7-71a05a252974
Sep 27 09:12:38.509: INFO: Couldn't delete PD "aws://ap-south-1a/vol-08120ecd7cf4169f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08120ecd7cf4169f0 is currently attached to i-028544abdfa483e39
	status code: 400, request id: 99f0de5a-b64d-4136-a69f-1fe8c94aea3c
Sep 27 09:12:44.611: INFO: Successfully deleted PD "aws://ap-south-1a/vol-08120ecd7cf4169f0".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 09:12:44.611: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5293" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:12:09.121: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 27 09:12:10.362: INFO: Creating resource for dynamic PV
Sep 27 09:12:10.362: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5279-e2e-sc5hx6z
STEP: creating a claim
Sep 27 09:12:10.606: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sb4p
STEP: Checking for subpath error in container status
Sep 27 09:12:25.816: INFO: Deleting pod "pod-subpath-test-dynamicpv-sb4p" in namespace "provisioning-5279"
Sep 27 09:12:26.060: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sb4p" to be fully deleted
STEP: Deleting pod
Sep 27 09:12:28.543: INFO: Deleting pod "pod-subpath-test-dynamicpv-sb4p" in namespace "provisioning-5279"
STEP: Deleting pvc
Sep 27 09:12:29.267: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comf6vsl"
... skipping 11 lines ...

• [SLOW TEST:37.088 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 54 lines ...
Sep 27 09:12:04.540: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7498-e2e-sczqxkv
STEP: creating a claim
Sep 27 09:12:04.775: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-chvl
STEP: Creating a pod to test subpath
Sep 27 09:12:05.497: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-chvl" in namespace "provisioning-7498" to be "Succeeded or Failed"
Sep 27 09:12:05.734: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 236.723843ms
Sep 27 09:12:07.970: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.472513714s
Sep 27 09:12:10.204: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.707058227s
Sep 27 09:12:12.446: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.948929446s
Sep 27 09:12:14.681: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 9.184268069s
Sep 27 09:12:16.917: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 11.42002595s
Sep 27 09:12:19.166: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.669214841s
Sep 27 09:12:21.401: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.903504012s
Sep 27 09:12:23.637: INFO: Pod "pod-subpath-test-dynamicpv-chvl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.139728597s
STEP: Saw pod success
Sep 27 09:12:23.637: INFO: Pod "pod-subpath-test-dynamicpv-chvl" satisfied condition "Succeeded or Failed"
Sep 27 09:12:23.871: INFO: Trying to get logs from node ip-172-20-46-234.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-chvl container test-container-volume-dynamicpv-chvl: <nil>
STEP: delete the pod
Sep 27 09:12:24.350: INFO: Waiting for pod pod-subpath-test-dynamicpv-chvl to disappear
Sep 27 09:12:24.584: INFO: Pod pod-subpath-test-dynamicpv-chvl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-chvl
Sep 27 09:12:24.584: INFO: Deleting pod "pod-subpath-test-dynamicpv-chvl" in namespace "provisioning-7498"
... skipping 29 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 09:12:06.256: 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.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 27 09:12:07.445: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 09:12:07.445: INFO: Creating resource for dynamic PV
Sep 27 09:12:07.445: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7259s2qx9
STEP: creating a claim
Sep 27 09:12:07.683: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7bcz
STEP: Checking for subpath error in container status
Sep 27 09:12:32.881: INFO: Deleting pod "pod-subpath-test-dynamicpv-7bcz" in namespace "provisioning-7259"
Sep 27 09:12:33.119: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7bcz" to be fully deleted
STEP: Deleting pod
Sep 27 09:12:35.594: INFO: Deleting pod "pod-subpath-test-dynamicpv-7bcz" in namespace "provisioning-7259"
STEP: Deleting pvc
Sep 27 09:12:36.308: INFO: Deleting PersistentVolumeClaim "awsljtdc"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.ITP296yt1/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 981 lines ...
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:27 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-065be949-478c-4782-b71f-55610e4bd96b" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:27 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-30519e29-bae0-4975-97f6-10c34e451c3f" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:28 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-a6917233-b198-4492-a162-0812da51ac2e" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:28 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-b08fc6a3-d411-4e57-b493-203786dd0c9d" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:28 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-f4cbc355-95c0-4850-b8b0-b473cb197814" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:30 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } SuccessfulAttachVolume: (combined from similar events): AttachVolume.Attach succeeded for volume "pvc-db00023d-9391-47b5-9115-48f8cb800a94" 
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:56 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-3bd2bb3a-eaf7-4ebb-95cc-b1eb738cc8cb" : rpc error: code = Internal desc = Could not attach volume "vol-021cb75264925d936" to node "i-01936d56116684286": attachment of disk "vol-021cb75264925d936" failed, expected device to be attached but was attaching
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:56 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } FailedAttachVolume: (combined from similar events): AttachVolume.Attach failed for volume "pvc-338fd707-cd85-4271-b5af-d79c74614a58" : rpc error: code = Internal desc = Could not attach volume "vol-08892f96922cf563e" to node "i-01936d56116684286": attachment of disk "vol-08892f96922cf563e" failed, expected device to be attached but was attaching
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:13:59 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-3fb3aaac-e7df-4125-a8f7-afdc2f31bda0" : rpc error: code = Internal desc = Could not attach volume "vol-0594bed1385197ee4" to node "i-01936d56116684286": attachment of disk "vol-0594bed1385197ee4" failed, expected device to be attached but was attaching
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:14:03 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-xqrt2" : failed to sync configmap cache: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:15:24 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume17 volume12 volume28 volume8 volume6 volume33 volume22 volume1 volume36 volume2 volume31 volume15 volume26], unattached volumes=[volume34 volume35 volume5 volume19 volume29 volume17 volume23 volume18 volume37 volume12 volume38 volume4 volume7 volume25 volume30 volume13 volume3 volume28 volume8 kube-api-access-xqrt2 volume32 volume24 volume6 volume33 volume14 volume22 volume1 volume36 volume39 volume2 volume9 volume21 volume31 volume15 volume27 volume16 volume26 volume10 volume20 volume11]: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:17:41 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume33 volume17 volume12 volume28 volume15 volume1 volume8 volume6 volume26 volume31 volume22 volume36 volume2], unattached volumes=[volume33 volume11 volume16 volume27 volume24 volume17 volume23 volume12 volume28 volume9 volume15 kube-api-access-xqrt2 volume35 volume14 volume10 volume5 volume1 volume4 volume37 volume8 volume21 volume7 volume13 volume29 volume18 volume6 volume26 volume34 volume31 volume39 volume30 volume20 volume22 volume32 volume19 volume36 volume2 volume38 volume3 volume25]: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:19:58 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1 volume22 volume33 volume17 volume28 volume31 volume26 volume15 volume8 volume36 volume2 volume6 volume12], unattached volumes=[volume38 volume1 volume16 volume22 volume4 volume27 volume3 volume20 volume33 volume5 volume21 volume17 kube-api-access-xqrt2 volume28 volume31 volume32 volume39 volume11 volume26 volume30 volume18 volume34 volume35 volume15 volume8 volume36 volume2 volume6 volume29 volume12 volume19 volume7 volume10 volume25 volume24 volume13 volume14 volume23 volume37 volume9]: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:22:16 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume28 volume22 volume17 volume15 volume1 volume12 volume31 volume36 volume8 volume2 volume6 volume26 volume33], unattached volumes=[volume25 volume27 volume28 volume22 volume17 volume18 volume23 volume15 volume38 volume39 volume10 volume1 volume13 volume37 volume4 volume11 volume21 volume30 volume12 volume20 volume32 volume31 kube-api-access-xqrt2 volume35 volume16 volume29 volume36 volume24 volume8 volume2 volume9 volume34 volume6 volume5 volume26 volume7 volume14 volume3 volume19 volume33]: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:24:30 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume26 volume36 volume33 volume8 volume6 volume28 volume2 volume22 volume12 volume31 volume17 volume15 volume1], unattached volumes=[volume14 volume26 volume36 kube-api-access-xqrt2 volume9 volume33 volume8 volume6 volume13 volume21 volume24 volume28 volume11 volume27 volume23 volume38 volume2 volume4 volume22 volume19 volume37 volume18 volume12 volume31 volume17 volume20 volume39 volume30 volume15 volume34 volume1 volume10 volume25 volume29 volume35 volume32 volume16 volume3 volume7 volume5]: timed out waiting for the condition
Sep 27 10:03:29.390: INFO: At 2021-09-27 09:26:46 +0000 UTC - event for pod-0934fda8-188f-44a4-b740-173df72af830: {kubelet ip-172-20-51-172.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume15 volume31 volume1 volume8 volume28 volume36 volume17 volume26 volume6 volume22 volume33 volume2 volume12], unattached volumes=[volume29 volume14 volume35 volume10 volume24 volume15 volume31 kube-api-access-xqrt2 volume7 volume1 volume5 volume25 volume38 volume30 volume16 volume8 volume28 volume36 volume39 volume9 volume4 volume17 volume20 volume37 volume26 volume6 volume23 volume13 volume3 volume22 volume32 volume18 volume19 volume21 volume33 volume2 volume12 volume11 volume34 volume27]: timed out waiting for the condition
... skipping 161 lines ...
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should support volume limits [Serial] [It]
    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123

    Unexpected error:
        <*errors.errorString | 0xc00021a0d0>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred

    /tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:202
------------------------------


Summarizing 1 Failure:

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits [It] should support volume limits [Serial] 
/tmp/kops.ITP296yt1/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:202

Ran 140 of 485 Specs in 3502.190 seconds
FAIL! -- 139 Passed | 1 Failed | 0 Pending | 345 Skipped


Ginkgo ran 1 suite in 59m31.933487639s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops --down
I0927 10:03:38.547380   26272 app.go:59] RunDir for this run: "/logs/artifacts/12325842-1f70-11ec-8af3-22f8e8a1ce5c"
I0927 10:03:38.547641   26272 app.go:90] ID for this run: "12325842-1f70-11ec-8af3-22f8e8a1ce5c"
I0927 10:03:38.582870   26272 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0927 10:03:38.602945   26284 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
... skipping 2618 lines ...