This job view page is being replaced by Spyglass soon. Check out the new job view.
PRrifelpet: Upgrade EBS CSI Driver to v1.4.0
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-13 13:58
Elapsed43m8s
Revision0b6c47d64719cf4e4cd2bd17a2e900f13eac807f
Refs 12529

No Test Failures!


Error lines from build-log.txt

... skipping 586 lines ...
I1013 14:03:59.364915   12542 app.go:90] ID for this run: "9237e933-2c2d-11ec-b555-ca1361d09b8c"
I1013 14:03:59.413792   12542 up.go:43] Cleaning up any leaked resources from previous cluster
I1013 14:03:59.413884   12542 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I1013 14:03:59.452847   12554 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 14:03:59.452956   12554 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 14:03:59.452961   12554 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
W1013 14:03:59.980984   12542 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1013 14:03:59.981057   12542 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --yes
I1013 14:04:00.017733   12564 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 14:04:00.017842   12564 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 14:04:00.017846   12564 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
I1013 14:04:00.500022   12542 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/13 14:04:00 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
I1013 14:04:00.513146   12542 http.go:37] curl https://ip.jsb.workers.dev
I1013 14:04:00.651533   12542 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-b6f7c24027-45100.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 35.225.131.181/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I1013 14:04:00.689575   12575 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 14:04:00.691883   12575 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 14:04:00.691891   12575 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 14:04:00.728127   12575 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 31 lines ...
I1013 14:04:21.786193   12542 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1013 14:04:21.823912   12595 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 14:04:21.824072   12595 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 14:04:21.824119   12595 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-b6f7c24027-45100.test-cncf-aws.k8s.io

W1013 14:04:23.691032   12595 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.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
W1013 14:04:33.727479   12595 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
W1013 14:04:43.768173   12595 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
W1013 14:04:53.803940   12595 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
W1013 14:05:03.853790   12595 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
W1013 14:05:13.887859   12595 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
W1013 14:05:23.920754   12595 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
W1013 14:05:33.973597   12595 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
W1013 14:05:44.009168   12595 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
W1013 14:05:54.056413   12595 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
W1013 14:06:04.092941   12595 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
W1013 14:06:14.149244   12595 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
W1013 14:06:24.195919   12595 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
W1013 14:06:34.228376   12595 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
W1013 14:06:44.266608   12595 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
W1013 14:06:54.310807   12595 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
W1013 14:07:04.361884   12595 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
W1013 14:07:14.400432   12595 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
W1013 14:07:24.432237   12595 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
W1013 14:07:34.529594   12595 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
W1013 14:07:44.563645   12595 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
W1013 14:07:54.598797   12595 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
W1013 14:08:04.632308   12595 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
W1013 14:08:14.673684   12595 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
W1013 14:08:24.708579   12595 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 13 lines ...
Pod	kube-system/coredns-6c8944dbdc-zwkb7			system-cluster-critical pod "coredns-6c8944dbdc-zwkb7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mrfct		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mrfct" is pending
Pod	kube-system/ebs-csi-controller-54dc46fc7b-ff72x		system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-ff72x" is pending
Pod	kube-system/ebs-csi-node-msk4z				system-node-critical pod "ebs-csi-node-msk4z" is pending
Pod	kube-system/ebs-csi-node-ps7tp				system-node-critical pod "ebs-csi-node-ps7tp" is pending

Validation Failed
W1013 14:08:40.199795   12595 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 19 lines ...
Pod	kube-system/ebs-csi-controller-54dc46fc7b-ff72x		system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-ff72x" is pending
Pod	kube-system/ebs-csi-node-msk4z				system-node-critical pod "ebs-csi-node-msk4z" is pending
Pod	kube-system/ebs-csi-node-nxwk9				system-node-critical pod "ebs-csi-node-nxwk9" is pending
Pod	kube-system/ebs-csi-node-ps7tp				system-node-critical pod "ebs-csi-node-ps7tp" is pending
Pod	kube-system/ebs-csi-node-qpc6t				system-node-critical pod "ebs-csi-node-qpc6t" is pending

Validation Failed
W1013 14:08:53.917717   12595 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 15 lines ...
Pod	kube-system/coredns-6c8944dbdc-zwkb7		system-cluster-critical pod "coredns-6c8944dbdc-zwkb7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mrfct	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mrfct" is pending
Pod	kube-system/ebs-csi-node-nxwk9			system-node-critical pod "ebs-csi-node-nxwk9" is pending
Pod	kube-system/ebs-csi-node-ps7tp			system-node-critical pod "ebs-csi-node-ps7tp" is pending
Pod	kube-system/ebs-csi-node-qpc6t			system-node-critical pod "ebs-csi-node-qpc6t" is pending

Validation Failed
W1013 14:09:07.809721   12595 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 13 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mrfct				system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mrfct" is pending
Pod	kube-system/ebs-csi-node-nxwk9						system-node-critical pod "ebs-csi-node-nxwk9" is pending
Pod	kube-system/ebs-csi-node-qpc6t						system-node-critical pod "ebs-csi-node-qpc6t" is pending
Pod	kube-system/ebs-csi-node-xv4m2						system-node-critical pod "ebs-csi-node-xv4m2" is pending
Pod	kube-system/kube-proxy-ip-172-20-55-40.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-55-40.ap-south-1.compute.internal" is pending

Validation Failed
W1013 14:09:21.542207   12595 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 10 lines ...
Pod	kube-system/calico-node-7txwl						system-node-critical pod "calico-node-7txwl" is not ready (calico-node)
Pod	kube-system/coredns-6c8944dbdc-5w5rc					system-cluster-critical pod "coredns-6c8944dbdc-5w5rc" is pending
Pod	kube-system/ebs-csi-node-qpc6t						system-node-critical pod "ebs-csi-node-qpc6t" is pending
Pod	kube-system/ebs-csi-node-xv4m2						system-node-critical pod "ebs-csi-node-xv4m2" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-186.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-186.ap-south-1.compute.internal" is pending

Validation Failed
W1013 14:09:35.198244   12595 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 6 lines ...
ip-172-20-57-186.ap-south-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-xv4m2	system-node-critical pod "ebs-csi-node-xv4m2" is pending

Validation Failed
W1013 14:09:48.889843   12595 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 358 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 257 lines ...
STEP: Creating a kubernetes client
Oct 13 14:13:22.444: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
W1013 14:13:24.108454   25182 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 14:13:24.108: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 14:13:25.071: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-south-1a]
Oct 13 14:13:25.073: 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] [3.350 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 289 lines ...
Oct 13 14:13:24.234: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5215kvd2l
STEP: creating a claim
Oct 13 14:13:24.481: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9nk5
STEP: Creating a pod to test subpath
Oct 13 14:13:25.250: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9nk5" in namespace "provisioning-5215" to be "Succeeded or Failed"
Oct 13 14:13:25.504: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 253.145828ms
Oct 13 14:13:27.751: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.500539966s
Oct 13 14:13:29.997: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.746214775s
Oct 13 14:13:32.243: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.992831819s
Oct 13 14:13:34.490: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.239525046s
Oct 13 14:13:36.738: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.487705745s
Oct 13 14:13:38.984: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.73359871s
Oct 13 14:13:41.235: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 15.984387259s
Oct 13 14:13:43.481: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.230494318s
Oct 13 14:13:45.728: INFO: Pod "pod-subpath-test-dynamicpv-9nk5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.477322242s
STEP: Saw pod success
Oct 13 14:13:45.728: INFO: Pod "pod-subpath-test-dynamicpv-9nk5" satisfied condition "Succeeded or Failed"
Oct 13 14:13:45.973: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-9nk5 container test-container-volume-dynamicpv-9nk5: <nil>
STEP: delete the pod
Oct 13 14:13:46.488: INFO: Waiting for pod pod-subpath-test-dynamicpv-9nk5 to disappear
Oct 13 14:13:46.732: INFO: Pod pod-subpath-test-dynamicpv-9nk5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9nk5
Oct 13 14:13:46.732: INFO: Deleting pod "pod-subpath-test-dynamicpv-9nk5" in namespace "provisioning-5215"
... skipping 194 lines ...
Oct 13 14:13:32.996: INFO: Creating resource for dynamic PV
Oct 13 14:13:32.997: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-93816kj5q
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 14:13:33.715: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 14:13:34.195: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:36.679: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:38.676: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:40.671: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:42.672: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:44.673: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:46.671: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:48.711: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:50.672: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:52.679: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:54.676: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:56.672: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:13:58.673: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:14:00.673: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:14:02.672: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:14:04.675: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-93816kj5q",
  	... // 3 identical fields
  }

Oct 13 14:14:05.152: INFO: Error updating pvc awsd8cpg: PersistentVolumeClaim "awsd8cpg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 97 lines ...
STEP: Deleting pod hostexec-ip-172-20-38-167.ap-south-1.compute.internal-vbww7 in namespace volumemode-5980
Oct 13 14:13:58.939: INFO: Deleting pod "pod-c2d321cc-d60f-43e1-abb4-de1863e91f1d" in namespace "volumemode-5980"
Oct 13 14:13:59.184: INFO: Wait up to 5m0s for pod "pod-c2d321cc-d60f-43e1-abb4-de1863e91f1d" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 14:14:01.671: INFO: Deleting PersistentVolumeClaim "pvc-kpg2n"
Oct 13 14:14:01.919: INFO: Deleting PersistentVolume "aws-2r8g6"
Oct 13 14:14:02.555: INFO: Couldn't delete PD "aws://ap-south-1a/vol-06149af433dcda492", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06149af433dcda492 is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 912a3e32-24d4-43bd-a151-1147f9e91a5e
Oct 13 14:14:08.708: INFO: Successfully deleted PD "aws://ap-south-1a/vol-06149af433dcda492".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:14:08.708: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5980" for this suite.
... skipping 41 lines ...
STEP: Creating a kubernetes client
Oct 13 14:13:22.353: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W1013 14:13:23.806457   25199 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 14:13:23.806: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 14:13:24.282: INFO: Creating resource for dynamic PV
Oct 13 14:13:24.282: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5753-e2e-scxtklg
STEP: creating a claim
Oct 13 14:13:24.526: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rvxj
STEP: Checking for subpath error in container status
Oct 13 14:13:53.757: INFO: Deleting pod "pod-subpath-test-dynamicpv-rvxj" in namespace "provisioning-5753"
Oct 13 14:13:54.000: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rvxj" to be fully deleted
STEP: Deleting pod
Oct 13 14:13:56.478: INFO: Deleting pod "pod-subpath-test-dynamicpv-rvxj" in namespace "provisioning-5753"
STEP: Deleting pvc
Oct 13 14:13:57.194: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjl2cb"
... skipping 11 lines ...

• [SLOW TEST:51.996 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Oct 13 14:13:26.302: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2721-e2e-sc686db
STEP: creating a claim
Oct 13 14:13:26.544: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-phdv
STEP: Creating a pod to test multi_subpath
Oct 13 14:13:27.267: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-phdv" in namespace "provisioning-2721" to be "Succeeded or Failed"
Oct 13 14:13:27.508: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 241.235626ms
Oct 13 14:13:29.750: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.482581133s
Oct 13 14:13:31.992: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.724664555s
Oct 13 14:13:34.234: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.967108815s
Oct 13 14:13:36.475: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 9.207715675s
Oct 13 14:13:38.715: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.44800391s
Oct 13 14:13:40.956: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.688580804s
Oct 13 14:13:43.197: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.929632458s
Oct 13 14:13:45.438: INFO: Pod "pod-subpath-test-dynamicpv-phdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.170882963s
STEP: Saw pod success
Oct 13 14:13:45.438: INFO: Pod "pod-subpath-test-dynamicpv-phdv" satisfied condition "Succeeded or Failed"
Oct 13 14:13:45.678: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-phdv container test-container-subpath-dynamicpv-phdv: <nil>
STEP: delete the pod
Oct 13 14:13:46.179: INFO: Waiting for pod pod-subpath-test-dynamicpv-phdv to disappear
Oct 13 14:13:46.419: INFO: Pod pod-subpath-test-dynamicpv-phdv no longer exists
STEP: Deleting pod
Oct 13 14:13:46.419: INFO: Deleting pod "pod-subpath-test-dynamicpv-phdv" in namespace "provisioning-2721"
... skipping 64 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 24 lines ...
Oct 13 14:13:35.409: INFO: PersistentVolumeClaim pvc-w8l8s found but phase is Pending instead of Bound.
Oct 13 14:13:37.648: INFO: PersistentVolumeClaim pvc-w8l8s found and phase=Bound (11.444014981s)
Oct 13 14:13:37.648: INFO: Waiting up to 3m0s for PersistentVolume aws-dzxtn to have phase Bound
Oct 13 14:13:37.886: INFO: PersistentVolume aws-dzxtn found and phase=Bound (237.953868ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-6hck
STEP: Creating a pod to test exec-volume-test
Oct 13 14:13:38.605: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-6hck" in namespace "volume-3208" to be "Succeeded or Failed"
Oct 13 14:13:38.843: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 237.873866ms
Oct 13 14:13:41.082: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476948795s
Oct 13 14:13:43.321: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 4.715695678s
Oct 13 14:13:45.561: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 6.955405822s
Oct 13 14:13:47.811: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 9.205728033s
Oct 13 14:13:50.050: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 11.444303385s
Oct 13 14:13:52.292: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 13.687046763s
Oct 13 14:13:54.530: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Pending", Reason="", readiness=false. Elapsed: 15.924883706s
Oct 13 14:13:56.769: INFO: Pod "exec-volume-test-preprovisionedpv-6hck": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.163934572s
STEP: Saw pod success
Oct 13 14:13:56.769: INFO: Pod "exec-volume-test-preprovisionedpv-6hck" satisfied condition "Succeeded or Failed"
Oct 13 14:13:57.008: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-6hck container exec-container-preprovisionedpv-6hck: <nil>
STEP: delete the pod
Oct 13 14:13:57.491: INFO: Waiting for pod exec-volume-test-preprovisionedpv-6hck to disappear
Oct 13 14:13:57.730: INFO: Pod exec-volume-test-preprovisionedpv-6hck no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-6hck
Oct 13 14:13:57.730: INFO: Deleting pod "exec-volume-test-preprovisionedpv-6hck" in namespace "volume-3208"
STEP: Deleting pv and pvc
Oct 13 14:13:57.967: INFO: Deleting PersistentVolumeClaim "pvc-w8l8s"
Oct 13 14:13:58.208: INFO: Deleting PersistentVolume "aws-dzxtn"
Oct 13 14:13:58.781: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0f1681a9a5fd70e96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1681a9a5fd70e96 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: e727f530-1de3-4952-bd74-00424b736db7
Oct 13 14:14:04.864: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0f1681a9a5fd70e96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1681a9a5fd70e96 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 86e8f0d1-6524-401d-93c1-e1eb9df2abd8
Oct 13 14:14:10.998: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0f1681a9a5fd70e96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1681a9a5fd70e96 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 6bd33943-9407-4520-b22a-198f706219d4
Oct 13 14:14:17.105: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0f1681a9a5fd70e96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1681a9a5fd70e96 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 50f3e89e-3a80-4fda-8f4d-f31fead46c0e
Oct 13 14:14:23.197: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0f1681a9a5fd70e96".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:14:23.197: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3208" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:13:26.448: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 14:13:27.666: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:13:27.666: INFO: Creating resource for dynamic PV
Oct 13 14:13:27.666: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5768f8ztf
STEP: creating a claim
Oct 13 14:13:27.912: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pbf6
STEP: Checking for subpath error in container status
Oct 13 14:13:59.139: INFO: Deleting pod "pod-subpath-test-dynamicpv-pbf6" in namespace "provisioning-5768"
Oct 13 14:13:59.384: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pbf6" to be fully deleted
STEP: Deleting pod
Oct 13 14:14:01.874: INFO: Deleting pod "pod-subpath-test-dynamicpv-pbf6" in namespace "provisioning-5768"
STEP: Deleting pvc
Oct 13 14:14:02.607: INFO: Deleting PersistentVolumeClaim "awsgtwg4"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 180 lines ...
Oct 13 14:14:27.263: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 106 lines ...
STEP: Deleting pod aws-client in namespace volume-6757
Oct 13 14:14:13.702: INFO: Waiting for pod aws-client to disappear
Oct 13 14:14:13.946: INFO: Pod aws-client still exists
Oct 13 14:14:15.947: INFO: Waiting for pod aws-client to disappear
Oct 13 14:14:16.192: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 14:14:16.554: INFO: Couldn't delete PD "aws://ap-south-1a/vol-091864ccb376081c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-091864ccb376081c3 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 1ca41f34-30db-41d7-bc3b-c7d771f480ec
Oct 13 14:14:22.634: INFO: Couldn't delete PD "aws://ap-south-1a/vol-091864ccb376081c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-091864ccb376081c3 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 74adbe2b-8263-47d7-adbf-5695ddfe44d4
Oct 13 14:14:28.749: INFO: Successfully deleted PD "aws://ap-south-1a/vol-091864ccb376081c3".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:14:28.749: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6757" for this suite.
... skipping 149 lines ...
Oct 13 14:13:29.319: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5818-e2e-scdzslg
STEP: creating a claim
Oct 13 14:13:29.564: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5lm5
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 14:13:30.342: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5lm5" in namespace "provisioning-5818" to be "Succeeded or Failed"
Oct 13 14:13:30.585: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 243.132001ms
Oct 13 14:13:32.829: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.486983311s
Oct 13 14:13:35.075: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.732758328s
Oct 13 14:13:37.319: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.976658515s
Oct 13 14:13:39.564: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.221838384s
Oct 13 14:13:41.812: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.470476854s
... skipping 8 lines ...
Oct 13 14:14:02.014: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Running", Reason="", readiness=true. Elapsed: 31.672492403s
Oct 13 14:14:04.260: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Running", Reason="", readiness=true. Elapsed: 33.917756055s
Oct 13 14:14:06.503: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Running", Reason="", readiness=true. Elapsed: 36.161350364s
Oct 13 14:14:08.748: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Running", Reason="", readiness=true. Elapsed: 38.40564975s
Oct 13 14:14:10.992: INFO: Pod "pod-subpath-test-dynamicpv-5lm5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.649848951s
STEP: Saw pod success
Oct 13 14:14:10.992: INFO: Pod "pod-subpath-test-dynamicpv-5lm5" satisfied condition "Succeeded or Failed"
Oct 13 14:14:11.235: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-5lm5 container test-container-subpath-dynamicpv-5lm5: <nil>
STEP: delete the pod
Oct 13 14:14:11.730: INFO: Waiting for pod pod-subpath-test-dynamicpv-5lm5 to disappear
Oct 13 14:14:11.972: INFO: Pod pod-subpath-test-dynamicpv-5lm5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5lm5
Oct 13 14:14:11.973: INFO: Deleting pod "pod-subpath-test-dynamicpv-5lm5" in namespace "provisioning-5818"
... skipping 49 lines ...

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

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

    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 64 lines ...
Oct 13 14:13:26.694: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7459ppvqd
STEP: creating a claim
Oct 13 14:13:26.945: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r4lw
STEP: Creating a pod to test subpath
Oct 13 14:13:27.684: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r4lw" in namespace "provisioning-7459" to be "Succeeded or Failed"
Oct 13 14:13:27.931: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 246.905731ms
Oct 13 14:13:30.177: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492801938s
Oct 13 14:13:32.424: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.739598754s
Oct 13 14:13:34.671: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.986549659s
Oct 13 14:13:36.917: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232690584s
Oct 13 14:13:39.167: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.482446078s
Oct 13 14:13:41.413: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.728726265s
Oct 13 14:13:43.660: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.975851994s
Oct 13 14:13:45.906: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.221809924s
Oct 13 14:13:48.153: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.468795662s
Oct 13 14:13:50.399: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.714763154s
STEP: Saw pod success
Oct 13 14:13:50.399: INFO: Pod "pod-subpath-test-dynamicpv-r4lw" satisfied condition "Succeeded or Failed"
Oct 13 14:13:50.644: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-r4lw container test-container-subpath-dynamicpv-r4lw: <nil>
STEP: delete the pod
Oct 13 14:13:51.180: INFO: Waiting for pod pod-subpath-test-dynamicpv-r4lw to disappear
Oct 13 14:13:51.425: INFO: Pod pod-subpath-test-dynamicpv-r4lw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r4lw
Oct 13 14:13:51.425: INFO: Deleting pod "pod-subpath-test-dynamicpv-r4lw" in namespace "provisioning-7459"
STEP: Creating pod pod-subpath-test-dynamicpv-r4lw
STEP: Creating a pod to test subpath
Oct 13 14:13:51.917: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r4lw" in namespace "provisioning-7459" to be "Succeeded or Failed"
Oct 13 14:13:52.162: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 245.101592ms
Oct 13 14:13:54.408: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491301982s
Oct 13 14:13:56.654: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.736972132s
Oct 13 14:13:58.901: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.983513637s
Oct 13 14:14:01.146: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 9.229093345s
Oct 13 14:14:03.393: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.475574575s
Oct 13 14:14:05.639: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.721856758s
Oct 13 14:14:07.885: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.967614444s
Oct 13 14:14:10.132: INFO: Pod "pod-subpath-test-dynamicpv-r4lw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.214848291s
STEP: Saw pod success
Oct 13 14:14:10.132: INFO: Pod "pod-subpath-test-dynamicpv-r4lw" satisfied condition "Succeeded or Failed"
Oct 13 14:14:10.377: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-r4lw container test-container-subpath-dynamicpv-r4lw: <nil>
STEP: delete the pod
Oct 13 14:14:10.886: INFO: Waiting for pod pod-subpath-test-dynamicpv-r4lw to disappear
Oct 13 14:14:11.131: INFO: Pod pod-subpath-test-dynamicpv-r4lw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r4lw
Oct 13 14:14:11.131: INFO: Deleting pod "pod-subpath-test-dynamicpv-r4lw" in namespace "provisioning-7459"
... skipping 415 lines ...
Oct 13 14:14:27.292: INFO: Waiting for pod aws-client to disappear
Oct 13 14:14:27.541: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 14:14:27.542: INFO: Deleting PersistentVolumeClaim "pvc-jkzlr"
Oct 13 14:14:27.784: INFO: Deleting PersistentVolume "aws-lxxgf"
Oct 13 14:14:28.371: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0162f1f07c4cd84fe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0162f1f07c4cd84fe is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: bc1660cd-8e6f-43d7-bb78-22bed2d5a485
Oct 13 14:14:34.473: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0162f1f07c4cd84fe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0162f1f07c4cd84fe is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 9be7abcf-6079-4e0f-b2bb-e70ad1aeeb90
Oct 13 14:14:40.604: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0162f1f07c4cd84fe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0162f1f07c4cd84fe is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 1b6b84b5-d69e-4118-ac48-83e466453c86
Oct 13 14:14:46.738: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0162f1f07c4cd84fe".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:14:46.738: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1069" for this suite.
... skipping 267 lines ...
Oct 13 14:13:24.221: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5798dqksv
STEP: creating a claim
Oct 13 14:13:24.466: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5z8p
STEP: Creating a pod to test subpath
Oct 13 14:13:25.239: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5z8p" in namespace "provisioning-5798" to be "Succeeded or Failed"
Oct 13 14:13:25.484: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 245.360202ms
Oct 13 14:13:27.730: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491299201s
Oct 13 14:13:29.978: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.739320947s
Oct 13 14:13:32.224: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.98543356s
Oct 13 14:13:34.470: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 9.231010735s
Oct 13 14:13:36.716: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 11.477451684s
... skipping 3 lines ...
Oct 13 14:13:45.703: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 20.464081544s
Oct 13 14:13:47.949: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 22.71007511s
Oct 13 14:13:50.194: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 24.955363733s
Oct 13 14:13:52.449: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Pending", Reason="", readiness=false. Elapsed: 27.21053917s
Oct 13 14:13:54.694: INFO: Pod "pod-subpath-test-dynamicpv-5z8p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.45543016s
STEP: Saw pod success
Oct 13 14:13:54.694: INFO: Pod "pod-subpath-test-dynamicpv-5z8p" satisfied condition "Succeeded or Failed"
Oct 13 14:13:54.939: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-5z8p container test-container-subpath-dynamicpv-5z8p: <nil>
STEP: delete the pod
Oct 13 14:13:55.441: INFO: Waiting for pod pod-subpath-test-dynamicpv-5z8p to disappear
Oct 13 14:13:55.689: INFO: Pod pod-subpath-test-dynamicpv-5z8p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5z8p
Oct 13 14:13:55.689: INFO: Deleting pod "pod-subpath-test-dynamicpv-5z8p" in namespace "provisioning-5798"
... skipping 285 lines ...
Oct 13 14:14:51.552: INFO: Waiting for pod aws-client to disappear
Oct 13 14:14:51.794: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 14:14:51.794: INFO: Deleting PersistentVolumeClaim "pvc-2qdj2"
Oct 13 14:14:52.035: INFO: Deleting PersistentVolume "aws-g8znw"
Oct 13 14:14:53.369: INFO: Couldn't delete PD "aws://ap-south-1a/vol-009d4fa3138dd2b0f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-009d4fa3138dd2b0f is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: e0154564-bee5-41a9-b81d-c29dfee42d12
Oct 13 14:14:59.463: INFO: Couldn't delete PD "aws://ap-south-1a/vol-009d4fa3138dd2b0f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-009d4fa3138dd2b0f is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: f21f1b35-e8f8-4512-a51c-32eecf09a28a
Oct 13 14:15:05.591: INFO: Successfully deleted PD "aws://ap-south-1a/vol-009d4fa3138dd2b0f".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:15:05.591: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7075" for this suite.
... skipping 113 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:14:10.918: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 14:14:12.138: INFO: Creating resource for dynamic PV
Oct 13 14:14:12.139: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4563-e2e-sc2xdb6
STEP: creating a claim
Oct 13 14:14:12.384: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zv8v
STEP: Checking for subpath error in container status
Oct 13 14:14:37.608: INFO: Deleting pod "pod-subpath-test-dynamicpv-zv8v" in namespace "provisioning-4563"
Oct 13 14:14:37.856: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zv8v" to be fully deleted
STEP: Deleting pod
Oct 13 14:14:40.347: INFO: Deleting pod "pod-subpath-test-dynamicpv-zv8v" in namespace "provisioning-4563"
STEP: Deleting pvc
Oct 13 14:14:41.080: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com962zp"
... skipping 14 lines ...

• [SLOW TEST:62.857 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:14:57.767: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:14:58.993: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 14:15:00.222: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-012eef3edef1045ac".
Oct 13 14:15:00.222: INFO: Creating resource for pre-provisioned PV
Oct 13 14:15:00.222: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 13 14:15:03.179: INFO: PersistentVolumeClaim pvc-fctvj found but phase is Pending instead of Bound.
Oct 13 14:15:05.417: INFO: PersistentVolumeClaim pvc-fctvj found but phase is Pending instead of Bound.
Oct 13 14:15:07.656: INFO: PersistentVolumeClaim pvc-fctvj found and phase=Bound (6.953719298s)
Oct 13 14:15:07.656: INFO: Waiting up to 3m0s for PersistentVolume aws-7jsvw to have phase Bound
Oct 13 14:15:07.896: INFO: PersistentVolume aws-7jsvw found and phase=Bound (239.740308ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:15:09.102: INFO: Deleting pod "pod-b98273c9-bc50-425e-aef0-511a78e92a4c" in namespace "volumemode-2940"
Oct 13 14:15:09.346: INFO: Wait up to 5m0s for pod "pod-b98273c9-bc50-425e-aef0-511a78e92a4c" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 14:15:11.827: INFO: Deleting PersistentVolumeClaim "pvc-fctvj"
Oct 13 14:15:12.066: INFO: Deleting PersistentVolume "aws-7jsvw"
Oct 13 14:15:12.645: INFO: Couldn't delete PD "aws://ap-south-1a/vol-012eef3edef1045ac", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-012eef3edef1045ac is currently attached to i-085e46da0253ca077
	status code: 400, request id: a30a341d-4e7b-4ff9-8d25-5739dfb26219
Oct 13 14:15:18.721: INFO: Successfully deleted PD "aws://ap-south-1a/vol-012eef3edef1045ac".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:15:18.721: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2940" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:15:19.212: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 14:15:20.645: INFO: found topology map[topology.kubernetes.io/zone:ap-south-1a]
Oct 13 14:15:20.645: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:15:20.645: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 11 lines ...
Oct 13 14:14:02.071: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3217-e2e-scb8sxv
STEP: creating a claim
Oct 13 14:14:02.319: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-67xx
STEP: Creating a pod to test subpath
Oct 13 14:14:03.061: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-3217" to be "Succeeded or Failed"
Oct 13 14:14:03.306: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 245.27456ms
Oct 13 14:14:05.553: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.492252117s
Oct 13 14:14:07.803: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.742689326s
Oct 13 14:14:10.051: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.990306229s
Oct 13 14:14:12.297: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 9.2367107s
Oct 13 14:14:14.543: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 11.482661667s
Oct 13 14:14:16.790: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 13.728799569s
Oct 13 14:14:19.036: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.975164774s
Oct 13 14:14:21.283: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.221979295s
Oct 13 14:14:23.530: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.46877369s
Oct 13 14:14:25.777: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.715806064s
Oct 13 14:14:28.023: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.96266431s
STEP: Saw pod success
Oct 13 14:14:28.024: INFO: Pod "pod-subpath-test-dynamicpv-67xx" satisfied condition "Succeeded or Failed"
Oct 13 14:14:28.269: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-67xx container test-container-subpath-dynamicpv-67xx: <nil>
STEP: delete the pod
Oct 13 14:14:28.785: INFO: Waiting for pod pod-subpath-test-dynamicpv-67xx to disappear
Oct 13 14:14:29.034: INFO: Pod pod-subpath-test-dynamicpv-67xx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-67xx
Oct 13 14:14:29.034: INFO: Deleting pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-3217"
STEP: Creating pod pod-subpath-test-dynamicpv-67xx
STEP: Creating a pod to test subpath
Oct 13 14:14:29.526: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-3217" to be "Succeeded or Failed"
Oct 13 14:14:29.775: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 248.917844ms
Oct 13 14:14:32.023: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.496612086s
Oct 13 14:14:34.269: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.742449751s
Oct 13 14:14:36.517: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.990412312s
Oct 13 14:14:38.763: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 9.236525697s
Oct 13 14:14:41.009: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 11.482692946s
... skipping 6 lines ...
Oct 13 14:14:56.736: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 27.209916521s
Oct 13 14:14:58.983: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 29.456511891s
Oct 13 14:15:01.229: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.702995888s
Oct 13 14:15:03.476: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.949932024s
Oct 13 14:15:05.723: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.197001167s
STEP: Saw pod success
Oct 13 14:15:05.723: INFO: Pod "pod-subpath-test-dynamicpv-67xx" satisfied condition "Succeeded or Failed"
Oct 13 14:15:05.974: INFO: Trying to get logs from node ip-172-20-38-167.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-67xx container test-container-subpath-dynamicpv-67xx: <nil>
STEP: delete the pod
Oct 13 14:15:06.480: INFO: Waiting for pod pod-subpath-test-dynamicpv-67xx to disappear
Oct 13 14:15:06.726: INFO: Pod pod-subpath-test-dynamicpv-67xx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-67xx
Oct 13 14:15:06.726: INFO: Deleting pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-3217"
... skipping 101 lines ...
Oct 13 14:14:54.280: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-21938rbq9
STEP: creating a claim
Oct 13 14:14:54.528: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 14:14:55.021: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 14:14:55.512: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:14:58.007: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:00.007: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:02.008: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:04.004: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:06.009: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:08.018: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:10.004: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:12.004: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:14.004: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:16.005: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:18.012: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:20.005: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:22.005: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:24.003: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:26.005: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-21938rbq9",
  	... // 3 identical fields
  }

Oct 13 14:15:26.496: INFO: Error updating pvc awsgvl2p: PersistentVolumeClaim "awsgvl2p" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 75 lines ...
Oct 13 14:14:31.963: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7945btwjq
STEP: creating a claim
Oct 13 14:14:32.217: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-nk2p
STEP: Creating a pod to test exec-volume-test
Oct 13 14:14:32.951: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-nk2p" in namespace "volume-7945" to be "Succeeded or Failed"
Oct 13 14:14:33.195: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 243.765036ms
Oct 13 14:14:35.440: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.489202986s
Oct 13 14:14:37.684: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.733268075s
Oct 13 14:14:39.928: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.977440656s
Oct 13 14:14:42.172: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 9.220952465s
Oct 13 14:14:44.416: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 11.464819892s
... skipping 2 lines ...
Oct 13 14:14:51.155: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 18.203969824s
Oct 13 14:14:53.400: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 20.448831631s
Oct 13 14:14:55.644: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 22.693151688s
Oct 13 14:14:57.890: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Pending", Reason="", readiness=false. Elapsed: 24.938657089s
Oct 13 14:15:00.135: INFO: Pod "exec-volume-test-dynamicpv-nk2p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.183757869s
STEP: Saw pod success
Oct 13 14:15:00.135: INFO: Pod "exec-volume-test-dynamicpv-nk2p" satisfied condition "Succeeded or Failed"
Oct 13 14:15:00.379: INFO: Trying to get logs from node ip-172-20-38-167.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-nk2p container exec-container-dynamicpv-nk2p: <nil>
STEP: delete the pod
Oct 13 14:15:00.887: INFO: Waiting for pod exec-volume-test-dynamicpv-nk2p to disappear
Oct 13 14:15:01.130: INFO: Pod exec-volume-test-dynamicpv-nk2p no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-nk2p
Oct 13 14:15:01.130: INFO: Deleting pod "exec-volume-test-dynamicpv-nk2p" in namespace "volume-7945"
... skipping 207 lines ...
Oct 13 14:14:35.584: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4159-e2e-sc26jjj
STEP: creating a claim
Oct 13 14:14:35.836: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dp4x
STEP: Creating a pod to test subpath
Oct 13 14:14:36.584: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dp4x" in namespace "provisioning-4159" to be "Succeeded or Failed"
Oct 13 14:14:36.829: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 245.389566ms
Oct 13 14:14:39.075: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491563105s
Oct 13 14:14:41.322: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.738666673s
Oct 13 14:14:43.569: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.985297s
Oct 13 14:14:45.816: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232719328s
Oct 13 14:14:48.062: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 11.478487186s
Oct 13 14:14:50.308: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 13.724246879s
Oct 13 14:14:52.554: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 15.97075129s
Oct 13 14:14:54.801: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 18.217401601s
Oct 13 14:14:57.049: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Pending", Reason="", readiness=false. Elapsed: 20.465212187s
Oct 13 14:14:59.296: INFO: Pod "pod-subpath-test-dynamicpv-dp4x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.712330781s
STEP: Saw pod success
Oct 13 14:14:59.296: INFO: Pod "pod-subpath-test-dynamicpv-dp4x" satisfied condition "Succeeded or Failed"
Oct 13 14:14:59.542: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-dp4x container test-container-volume-dynamicpv-dp4x: <nil>
STEP: delete the pod
Oct 13 14:15:00.042: INFO: Waiting for pod pod-subpath-test-dynamicpv-dp4x to disappear
Oct 13 14:15:00.287: INFO: Pod pod-subpath-test-dynamicpv-dp4x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dp4x
Oct 13 14:15:00.287: INFO: Deleting pod "pod-subpath-test-dynamicpv-dp4x" in namespace "provisioning-4159"
... skipping 115 lines ...
Oct 13 14:15:02.337: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3080-e2e-scrkkb8
STEP: creating a claim
Oct 13 14:15:02.584: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-shpm
STEP: Creating a pod to test subpath
Oct 13 14:15:03.334: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-shpm" in namespace "provisioning-3080" to be "Succeeded or Failed"
Oct 13 14:15:03.579: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 244.79686ms
Oct 13 14:15:05.825: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490997087s
Oct 13 14:15:08.071: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.736978056s
Oct 13 14:15:10.317: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.982215456s
Oct 13 14:15:12.562: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 9.227562462s
Oct 13 14:15:14.808: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Pending", Reason="", readiness=false. Elapsed: 11.473748626s
Oct 13 14:15:17.055: INFO: Pod "pod-subpath-test-dynamicpv-shpm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.720205786s
STEP: Saw pod success
Oct 13 14:15:17.055: INFO: Pod "pod-subpath-test-dynamicpv-shpm" satisfied condition "Succeeded or Failed"
Oct 13 14:15:17.302: INFO: Trying to get logs from node ip-172-20-38-167.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-shpm container test-container-subpath-dynamicpv-shpm: <nil>
STEP: delete the pod
Oct 13 14:15:17.807: INFO: Waiting for pod pod-subpath-test-dynamicpv-shpm to disappear
Oct 13 14:15:18.051: INFO: Pod pod-subpath-test-dynamicpv-shpm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-shpm
Oct 13 14:15:18.051: INFO: Deleting pod "pod-subpath-test-dynamicpv-shpm" in namespace "provisioning-3080"
... skipping 416 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 401 lines ...
Oct 13 14:15:29.613: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 14:15:30.846: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-0d53976d72541db67".
Oct 13 14:15:30.847: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lptz
STEP: Creating a pod to test exec-volume-test
Oct 13 14:15:31.097: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lptz" in namespace "volume-8974" to be "Succeeded or Failed"
Oct 13 14:15:31.342: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 245.277523ms
Oct 13 14:15:33.588: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491317007s
Oct 13 14:15:35.835: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.737729707s
Oct 13 14:15:38.082: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.98524445s
Oct 13 14:15:40.328: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 9.230500111s
Oct 13 14:15:42.573: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Pending", Reason="", readiness=false. Elapsed: 11.476332259s
Oct 13 14:15:44.820: INFO: Pod "exec-volume-test-inlinevolume-lptz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.722638008s
STEP: Saw pod success
Oct 13 14:15:44.820: INFO: Pod "exec-volume-test-inlinevolume-lptz" satisfied condition "Succeeded or Failed"
Oct 13 14:15:45.065: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-lptz container exec-container-inlinevolume-lptz: <nil>
STEP: delete the pod
Oct 13 14:15:45.564: INFO: Waiting for pod exec-volume-test-inlinevolume-lptz to disappear
Oct 13 14:15:45.809: INFO: Pod exec-volume-test-inlinevolume-lptz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lptz
Oct 13 14:15:45.809: INFO: Deleting pod "exec-volume-test-inlinevolume-lptz" in namespace "volume-8974"
Oct 13 14:15:46.407: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0d53976d72541db67", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d53976d72541db67 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 8ec78c0c-c87b-4267-8402-db99492e5a24
Oct 13 14:15:52.580: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0d53976d72541db67", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d53976d72541db67 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 1d85257b-c872-439e-af66-8cfe69e3e948
Oct 13 14:15:58.720: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0d53976d72541db67".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:15:58.721: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8974" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:15:13.777: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 14:15:15.000: INFO: Creating resource for dynamic PV
Oct 13 14:15:15.000: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4294-e2e-sc5fxln
STEP: creating a claim
Oct 13 14:15:15.245: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-96r5
STEP: Checking for subpath error in container status
Oct 13 14:15:42.470: INFO: Deleting pod "pod-subpath-test-dynamicpv-96r5" in namespace "provisioning-4294"
Oct 13 14:15:42.718: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-96r5" to be fully deleted
STEP: Deleting pod
Oct 13 14:15:47.205: INFO: Deleting pod "pod-subpath-test-dynamicpv-96r5" in namespace "provisioning-4294"
STEP: Deleting pvc
Oct 13 14:15:47.939: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvbr6z"
... skipping 11 lines ...

• [SLOW TEST:51.122 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 400 lines ...
Oct 13 14:15:37.261: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2556wrjzp
STEP: creating a claim
Oct 13 14:15:37.506: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-glzn
STEP: Creating a pod to test multi_subpath
Oct 13 14:15:38.270: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-glzn" in namespace "provisioning-2556" to be "Succeeded or Failed"
Oct 13 14:15:38.515: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 244.636507ms
Oct 13 14:15:40.760: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.489797797s
Oct 13 14:15:43.006: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.73565723s
Oct 13 14:15:45.252: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.981578434s
Oct 13 14:15:47.497: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 9.22707304s
Oct 13 14:15:49.743: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 11.473056497s
Oct 13 14:15:51.988: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 13.718516396s
Oct 13 14:15:54.234: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 15.963780002s
Oct 13 14:15:56.479: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.209201249s
Oct 13 14:15:58.732: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.461945292s
Oct 13 14:16:00.978: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.708115424s
Oct 13 14:16:03.225: INFO: Pod "pod-subpath-test-dynamicpv-glzn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.95490584s
STEP: Saw pod success
Oct 13 14:16:03.225: INFO: Pod "pod-subpath-test-dynamicpv-glzn" satisfied condition "Succeeded or Failed"
Oct 13 14:16:03.470: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-glzn container test-container-subpath-dynamicpv-glzn: <nil>
STEP: delete the pod
Oct 13 14:16:03.967: INFO: Waiting for pod pod-subpath-test-dynamicpv-glzn to disappear
Oct 13 14:16:04.212: INFO: Pod pod-subpath-test-dynamicpv-glzn no longer exists
STEP: Deleting pod
Oct 13 14:16:04.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-glzn" in namespace "provisioning-2556"
... skipping 120 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:15:36.759: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 14:15:37.962: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:15:37.962: INFO: Creating resource for dynamic PV
Oct 13 14:15:37.962: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7388qcjnx
STEP: creating a claim
Oct 13 14:15:38.200: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zbvg
STEP: Checking for subpath error in container status
Oct 13 14:16:03.397: INFO: Deleting pod "pod-subpath-test-dynamicpv-zbvg" in namespace "provisioning-7388"
Oct 13 14:16:03.639: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zbvg" to be fully deleted
STEP: Deleting pod
Oct 13 14:16:06.115: INFO: Deleting pod "pod-subpath-test-dynamicpv-zbvg" in namespace "provisioning-7388"
STEP: Deleting pvc
Oct 13 14:16:06.830: INFO: Deleting PersistentVolumeClaim "aws2xknw"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 234 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:15:43.518: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:15:44.758: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:15:44.758: INFO: Creating resource for dynamic PV
Oct 13 14:15:44.758: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6488nvtqt
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:15:50.484: INFO: Deleting pod "pod-21da4dc5-2c66-491e-824c-9aa58ca58be6" in namespace "volumemode-6488"
Oct 13 14:15:50.730: INFO: Wait up to 5m0s for pod "pod-21da4dc5-2c66-491e-824c-9aa58ca58be6" to be fully deleted
STEP: Deleting pvc
Oct 13 14:15:53.714: INFO: Deleting PersistentVolumeClaim "aws2vwp6"
Oct 13 14:15:53.960: INFO: Waiting up to 5m0s for PersistentVolume pvc-1615e6d4-9182-4489-927c-df89ce15a5f3 to get deleted
Oct 13 14:15:54.205: INFO: PersistentVolume pvc-1615e6d4-9182-4489-927c-df89ce15a5f3 found and phase=Released (244.804261ms)
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:16:05.408: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:16:06.609: INFO: Creating resource for dynamic PV
Oct 13 14:16:06.609: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8977-e2e-scrsdjp
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:16:12.312: INFO: Deleting pod "pod-390b74f8-88b9-4a2e-8cdf-e628dbba5978" in namespace "volumemode-8977"
Oct 13 14:16:12.554: INFO: Wait up to 5m0s for pod "pod-390b74f8-88b9-4a2e-8cdf-e628dbba5978" to be fully deleted
STEP: Deleting pvc
Oct 13 14:16:15.516: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2tdnb"
Oct 13 14:16:15.757: INFO: Waiting up to 5m0s for PersistentVolume pvc-8c392642-9b22-43df-8d49-ced19bdbc4a2 to get deleted
Oct 13 14:16:15.997: INFO: PersistentVolume pvc-8c392642-9b22-43df-8d49-ced19bdbc4a2 found and phase=Released (240.094777ms)
... skipping 9 lines ...

• [SLOW TEST:27.047 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] vcp at scale [Feature:vsphere] 
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:16:32.457: INFO: >>> kubeConfig: /root/.kube/config
... skipping 107 lines ...
Oct 13 14:16:19.513: INFO: Waiting for pod aws-client to disappear
Oct 13 14:16:19.752: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 14:16:19.752: INFO: Deleting PersistentVolumeClaim "pvc-zgglp"
Oct 13 14:16:20.004: INFO: Deleting PersistentVolume "aws-2h9kx"
Oct 13 14:16:21.379: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0d5c6b07494e3182d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d5c6b07494e3182d is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 839522c6-afb1-47e3-9e71-fba3564cbd36
Oct 13 14:16:27.488: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0d5c6b07494e3182d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d5c6b07494e3182d is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 6366820f-dc57-4673-8e83-7fde28c797e8
Oct 13 14:16:33.565: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0d5c6b07494e3182d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d5c6b07494e3182d is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: a8a1cd12-ad73-475e-aaf4-63285218d0f7
Oct 13 14:16:39.685: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0d5c6b07494e3182d".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:16:39.685: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3257" for this suite.
... skipping 35 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:15:57.306: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:15:58.544: INFO: Creating resource for dynamic PV
Oct 13 14:15:58.544: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6782-e2e-sc4wf88
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:16:04.272: INFO: Deleting pod "pod-b31fe1a2-81d6-4539-b267-dfd5771f2209" in namespace "volumemode-6782"
Oct 13 14:16:04.522: INFO: Wait up to 5m0s for pod "pod-b31fe1a2-81d6-4539-b267-dfd5771f2209" to be fully deleted
STEP: Deleting pvc
Oct 13 14:16:07.502: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.combk54c"
Oct 13 14:16:07.755: INFO: Waiting up to 5m0s for PersistentVolume pvc-482299eb-d23e-4118-a00e-6d0de44f52c6 to get deleted
Oct 13 14:16:08.001: INFO: PersistentVolume pvc-482299eb-d23e-4118-a00e-6d0de44f52c6 found and phase=Released (246.214937ms)
... skipping 13 lines ...

• [SLOW TEST:48.171 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 14:16:45.479: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 234 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

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

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

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

    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 508 lines ...
Oct 13 14:15:47.373: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8702-e2e-sc94q6d
STEP: creating a claim
Oct 13 14:15:47.612: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5fvp
STEP: Creating a pod to test exec-volume-test
Oct 13 14:15:48.332: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5fvp" in namespace "volume-8702" to be "Succeeded or Failed"
Oct 13 14:15:48.569: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 237.372559ms
Oct 13 14:15:50.812: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.480792266s
Oct 13 14:15:53.051: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.719673456s
Oct 13 14:15:55.289: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.95756411s
Oct 13 14:15:57.526: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.19482802s
Oct 13 14:15:59.765: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.433154768s
... skipping 8 lines ...
Oct 13 14:16:19.908: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 31.576834271s
Oct 13 14:16:22.147: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 33.81494632s
Oct 13 14:16:24.384: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.052629708s
Oct 13 14:16:26.623: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Pending", Reason="", readiness=false. Elapsed: 38.291567886s
Oct 13 14:16:28.898: INFO: Pod "exec-volume-test-dynamicpv-5fvp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.566496446s
STEP: Saw pod success
Oct 13 14:16:28.898: INFO: Pod "exec-volume-test-dynamicpv-5fvp" satisfied condition "Succeeded or Failed"
Oct 13 14:16:29.136: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-5fvp container exec-container-dynamicpv-5fvp: <nil>
STEP: delete the pod
Oct 13 14:16:29.620: INFO: Waiting for pod exec-volume-test-dynamicpv-5fvp to disappear
Oct 13 14:16:29.857: INFO: Pod exec-volume-test-dynamicpv-5fvp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5fvp
Oct 13 14:16:29.857: INFO: Deleting pod "exec-volume-test-dynamicpv-5fvp" in namespace "volume-8702"
... skipping 1220 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 51 lines ...
Oct 13 14:17:00.919: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7514-e2e-scrxpb7
STEP: creating a claim
Oct 13 14:17:01.159: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ldlv
STEP: Creating a pod to test subpath
Oct 13 14:17:01.883: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ldlv" in namespace "provisioning-7514" to be "Succeeded or Failed"
Oct 13 14:17:02.122: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 239.458572ms
Oct 13 14:17:04.362: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.479545572s
Oct 13 14:17:06.602: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.719815506s
Oct 13 14:17:08.843: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.960851894s
Oct 13 14:17:11.083: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 9.200668255s
Oct 13 14:17:13.323: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.440069831s
... skipping 7 lines ...
Oct 13 14:17:31.245: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 29.362876642s
Oct 13 14:17:33.485: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.602460996s
Oct 13 14:17:35.726: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 33.842995395s
Oct 13 14:17:37.966: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Pending", Reason="", readiness=false. Elapsed: 36.083246837s
Oct 13 14:17:40.207: INFO: Pod "pod-subpath-test-dynamicpv-ldlv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.324154607s
STEP: Saw pod success
Oct 13 14:17:40.207: INFO: Pod "pod-subpath-test-dynamicpv-ldlv" satisfied condition "Succeeded or Failed"
Oct 13 14:17:40.446: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-ldlv container test-container-subpath-dynamicpv-ldlv: <nil>
STEP: delete the pod
Oct 13 14:17:40.935: INFO: Waiting for pod pod-subpath-test-dynamicpv-ldlv to disappear
Oct 13 14:17:41.174: INFO: Pod pod-subpath-test-dynamicpv-ldlv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ldlv
Oct 13 14:17:41.174: INFO: Deleting pod "pod-subpath-test-dynamicpv-ldlv" in namespace "provisioning-7514"
... skipping 379 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:17:41.519: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:17:42.707: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 14:17:44.094: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-04212c0a9eecf83e5".
Oct 13 14:17:44.094: INFO: Creating resource for pre-provisioned PV
Oct 13 14:17:44.094: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 13 14:17:47.047: INFO: PersistentVolumeClaim pvc-zt7mr found but phase is Pending instead of Bound.
Oct 13 14:17:49.285: INFO: PersistentVolumeClaim pvc-zt7mr found but phase is Pending instead of Bound.
Oct 13 14:17:51.522: INFO: PersistentVolumeClaim pvc-zt7mr found and phase=Bound (6.95158661s)
Oct 13 14:17:51.522: INFO: Waiting up to 3m0s for PersistentVolume aws-z92lv to have phase Bound
Oct 13 14:17:51.759: INFO: PersistentVolume aws-z92lv found and phase=Bound (236.78044ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:17:55.186: INFO: Deleting pod "pod-941ae04a-3d59-4931-ac83-77bf23248335" in namespace "volumemode-1667"
Oct 13 14:17:55.424: INFO: Wait up to 5m0s for pod "pod-941ae04a-3d59-4931-ac83-77bf23248335" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 14:17:57.902: INFO: Deleting PersistentVolumeClaim "pvc-zt7mr"
Oct 13 14:17:58.141: INFO: Deleting PersistentVolume "aws-z92lv"
Oct 13 14:17:58.735: INFO: Couldn't delete PD "aws://ap-south-1a/vol-04212c0a9eecf83e5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04212c0a9eecf83e5 is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 91924c52-6187-4a2f-b1b1-e9c409ea4517
Oct 13 14:18:04.898: INFO: Successfully deleted PD "aws://ap-south-1a/vol-04212c0a9eecf83e5".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:18:04.899: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1667" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 14:18:05.380: INFO: Driver aws doesn't publish storage capacity -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] capacity
... skipping 186 lines ...
Oct 13 14:17:43.220: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1969-e2e-scdjglq
STEP: creating a claim
Oct 13 14:17:43.459: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 14:17:43.942: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 14:17:44.419: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:46.897: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:48.899: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:50.898: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:52.896: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:54.906: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:56.897: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:17:58.903: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:00.896: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:02.902: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:04.900: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:06.899: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:08.896: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:10.897: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:12.898: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:14.899: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1969-e2e-scdjglq",
  	... // 3 identical fields
  }

Oct 13 14:18:15.376: INFO: Error updating pvc ebs.csi.aws.comllhl6: PersistentVolumeClaim "ebs.csi.aws.comllhl6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 168 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:17:53.477: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 14:17:54.705: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:17:54.705: INFO: Creating resource for dynamic PV
Oct 13 14:17:54.705: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4057jxspz
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 14:18:00.441: INFO: Deleting pod "pod-cba419b7-69d0-4b0a-9e55-04207eccb3c9" in namespace "volumemode-4057"
Oct 13 14:18:00.687: INFO: Wait up to 5m0s for pod "pod-cba419b7-69d0-4b0a-9e55-04207eccb3c9" to be fully deleted
STEP: Deleting pvc
Oct 13 14:18:03.671: INFO: Deleting PersistentVolumeClaim "awschcnr"
Oct 13 14:18:03.918: INFO: Waiting up to 5m0s for PersistentVolume pvc-c19b4aff-0e45-4b0c-b481-b569d1ea016b to get deleted
Oct 13 14:18:04.165: INFO: PersistentVolume pvc-c19b4aff-0e45-4b0c-b481-b569d1ea016b found and phase=Released (246.686981ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 120 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:18:20.647: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 14:18:22.122: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-south-1a]
Oct 13 14:18:22.123: 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.214 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 63 lines ...
Oct 13 14:18:05.315: INFO: PersistentVolumeClaim pvc-lt9k5 found but phase is Pending instead of Bound.
Oct 13 14:18:07.561: INFO: PersistentVolumeClaim pvc-lt9k5 found and phase=Bound (4.733310427s)
Oct 13 14:18:07.561: INFO: Waiting up to 3m0s for PersistentVolume aws-bv2zr to have phase Bound
Oct 13 14:18:07.806: INFO: PersistentVolume aws-bv2zr found and phase=Bound (244.950074ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-l9hg
STEP: Creating a pod to test exec-volume-test
Oct 13 14:18:08.537: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-l9hg" in namespace "volume-9001" to be "Succeeded or Failed"
Oct 13 14:18:08.780: INFO: Pod "exec-volume-test-preprovisionedpv-l9hg": Phase="Pending", Reason="", readiness=false. Elapsed: 242.84342ms
Oct 13 14:18:11.024: INFO: Pod "exec-volume-test-preprovisionedpv-l9hg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.486506467s
Oct 13 14:18:13.267: INFO: Pod "exec-volume-test-preprovisionedpv-l9hg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.729877933s
Oct 13 14:18:15.512: INFO: Pod "exec-volume-test-preprovisionedpv-l9hg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.974664125s
STEP: Saw pod success
Oct 13 14:18:15.512: INFO: Pod "exec-volume-test-preprovisionedpv-l9hg" satisfied condition "Succeeded or Failed"
Oct 13 14:18:15.755: INFO: Trying to get logs from node ip-172-20-38-167.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-l9hg container exec-container-preprovisionedpv-l9hg: <nil>
STEP: delete the pod
Oct 13 14:18:16.256: INFO: Waiting for pod exec-volume-test-preprovisionedpv-l9hg to disappear
Oct 13 14:18:16.502: INFO: Pod exec-volume-test-preprovisionedpv-l9hg no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-l9hg
Oct 13 14:18:16.503: INFO: Deleting pod "exec-volume-test-preprovisionedpv-l9hg" in namespace "volume-9001"
STEP: Deleting pv and pvc
Oct 13 14:18:16.746: INFO: Deleting PersistentVolumeClaim "pvc-lt9k5"
Oct 13 14:18:16.990: INFO: Deleting PersistentVolume "aws-bv2zr"
Oct 13 14:18:17.574: INFO: Couldn't delete PD "aws://ap-south-1a/vol-09534e66d57940bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09534e66d57940bae is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 69bc3f15-1e9d-4978-bc08-943365be0443
Oct 13 14:18:23.662: INFO: Couldn't delete PD "aws://ap-south-1a/vol-09534e66d57940bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09534e66d57940bae is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 5c79426c-4c95-49b4-ae0c-41764322b647
Oct 13 14:18:29.837: INFO: Couldn't delete PD "aws://ap-south-1a/vol-09534e66d57940bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09534e66d57940bae is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 4a907def-47cb-493b-8526-b6d8989e4006
Oct 13 14:18:35.957: INFO: Successfully deleted PD "aws://ap-south-1a/vol-09534e66d57940bae".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:18:35.957: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9001" for this suite.
... skipping 18 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 56 lines ...
Oct 13 14:18:06.568: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7012r6j6r
STEP: creating a claim
Oct 13 14:18:06.806: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dcbs
STEP: Creating a pod to test exec-volume-test
Oct 13 14:18:07.555: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dcbs" in namespace "volume-7012" to be "Succeeded or Failed"
Oct 13 14:18:07.793: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 237.71179ms
Oct 13 14:18:10.031: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.475104276s
Oct 13 14:18:12.268: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.712667962s
Oct 13 14:18:14.509: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.953946083s
Oct 13 14:18:16.747: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 9.191213995s
Oct 13 14:18:18.985: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 11.429312987s
Oct 13 14:18:21.223: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Pending", Reason="", readiness=false. Elapsed: 13.667501743s
Oct 13 14:18:23.460: INFO: Pod "exec-volume-test-dynamicpv-dcbs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.904922475s
STEP: Saw pod success
Oct 13 14:18:23.461: INFO: Pod "exec-volume-test-dynamicpv-dcbs" satisfied condition "Succeeded or Failed"
Oct 13 14:18:23.697: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-dcbs container exec-container-dynamicpv-dcbs: <nil>
STEP: delete the pod
Oct 13 14:18:24.188: INFO: Waiting for pod exec-volume-test-dynamicpv-dcbs to disappear
Oct 13 14:18:24.425: INFO: Pod exec-volume-test-dynamicpv-dcbs no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dcbs
Oct 13 14:18:24.425: INFO: Deleting pod "exec-volume-test-dynamicpv-dcbs" in namespace "volume-7012"
... skipping 57 lines ...

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

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

    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 11 lines ...
Oct 13 14:18:06.585: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2762-e2e-scq7sp5
STEP: creating a claim
Oct 13 14:18:06.824: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-spss
STEP: Creating a pod to test subpath
Oct 13 14:18:07.577: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-spss" in namespace "provisioning-2762" to be "Succeeded or Failed"
Oct 13 14:18:07.818: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 241.242967ms
Oct 13 14:18:10.062: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 2.48470758s
Oct 13 14:18:12.300: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 4.722723226s
Oct 13 14:18:14.539: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 6.962123475s
Oct 13 14:18:16.778: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 9.200942717s
Oct 13 14:18:19.018: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 11.440866931s
Oct 13 14:18:21.256: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 13.679272986s
Oct 13 14:18:23.496: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Pending", Reason="", readiness=false. Elapsed: 15.918553543s
Oct 13 14:18:25.734: INFO: Pod "pod-subpath-test-dynamicpv-spss": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.157294067s
STEP: Saw pod success
Oct 13 14:18:25.734: INFO: Pod "pod-subpath-test-dynamicpv-spss" satisfied condition "Succeeded or Failed"
Oct 13 14:18:25.972: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-spss container test-container-subpath-dynamicpv-spss: <nil>
STEP: delete the pod
Oct 13 14:18:26.467: INFO: Waiting for pod pod-subpath-test-dynamicpv-spss to disappear
Oct 13 14:18:26.712: INFO: Pod pod-subpath-test-dynamicpv-spss no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-spss
Oct 13 14:18:26.713: INFO: Deleting pod "pod-subpath-test-dynamicpv-spss" in namespace "provisioning-2762"
... skipping 77 lines ...
Oct 13 14:17:55.141: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-65909jdcq      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-6590    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-65909jdcq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6590    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-65909jdcq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6590    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-65909jdcq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-65909jdcq    8aac3c6b-e336-49c2-9da7-edd89df246fd 9310 0 2021-10-13 14:17:55 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 14:17:55 +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-vjkn6 pvc- provisioning-6590  811bcf06-fe7f-4c7f-9a81-6cb74e167ba2 9325 0 2021-10-13 14:17:56 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 14:17:56 +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-65909jdcq,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-83eeb30b-2cad-465f-b3e2-99fe766591ac in namespace provisioning-6590
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 14:18:11.771: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-lzzgh" in namespace "provisioning-6590" to be "Succeeded or Failed"
Oct 13 14:18:12.009: INFO: Pod "pvc-volume-tester-writer-lzzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 237.923748ms
Oct 13 14:18:14.248: INFO: Pod "pvc-volume-tester-writer-lzzgh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.476606734s
STEP: Saw pod success
Oct 13 14:18:14.248: INFO: Pod "pvc-volume-tester-writer-lzzgh" satisfied condition "Succeeded or Failed"
Oct 13 14:18:14.736: INFO: Pod pvc-volume-tester-writer-lzzgh has the following logs: 
Oct 13 14:18:14.737: INFO: Deleting pod "pvc-volume-tester-writer-lzzgh" in namespace "provisioning-6590"
Oct 13 14:18:14.979: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-lzzgh" 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-54-148.ap-south-1.compute.internal"
Oct 13 14:18:15.932: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-s9x2w" in namespace "provisioning-6590" to be "Succeeded or Failed"
Oct 13 14:18:16.169: INFO: Pod "pvc-volume-tester-reader-s9x2w": Phase="Pending", Reason="", readiness=false. Elapsed: 237.519625ms
Oct 13 14:18:18.408: INFO: Pod "pvc-volume-tester-reader-s9x2w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476758449s
Oct 13 14:18:20.648: INFO: Pod "pvc-volume-tester-reader-s9x2w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.716106108s
STEP: Saw pod success
Oct 13 14:18:20.648: INFO: Pod "pvc-volume-tester-reader-s9x2w" satisfied condition "Succeeded or Failed"
Oct 13 14:18:21.127: INFO: Pod pvc-volume-tester-reader-s9x2w has the following logs: hello world

Oct 13 14:18:21.127: INFO: Deleting pod "pvc-volume-tester-reader-s9x2w" in namespace "provisioning-6590"
Oct 13 14:18:21.373: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-s9x2w" to be fully deleted
Oct 13 14:18:21.610: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-vjkn6] to have phase Bound
Oct 13 14:18:21.848: INFO: PersistentVolumeClaim pvc-vjkn6 found and phase=Bound (237.423724ms)
... skipping 88 lines ...

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

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

    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 76 lines ...
Oct 13 14:16:35.354: INFO: Creating resource for dynamic PV
Oct 13 14:16:35.354: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2276-e2e-scjqrd2
STEP: creating a claim
Oct 13 14:16:35.595: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-2276
Oct 13 14:16:36.321: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-2276" in namespace "provisioning-2276" to be "Succeeded or Failed"
Oct 13 14:16:36.561: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 239.96409ms
Oct 13 14:16:38.801: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 2.480661917s
Oct 13 14:16:41.041: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 4.720851557s
Oct 13 14:16:43.283: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 6.962653616s
Oct 13 14:16:45.524: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 9.203099909s
Oct 13 14:16:47.766: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 11.445378024s
... skipping 24 lines ...
Oct 13 14:17:43.872: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.551828001s
Oct 13 14:17:46.118: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.797293842s
Oct 13 14:17:48.365: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 1m12.044569939s
Oct 13 14:17:50.610: INFO: Pod "volume-prep-provisioning-2276": Phase="Pending", Reason="", readiness=false. Elapsed: 1m14.289785501s
Oct 13 14:17:52.856: INFO: Pod "volume-prep-provisioning-2276": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m16.535259656s
STEP: Saw pod success
Oct 13 14:17:52.856: INFO: Pod "volume-prep-provisioning-2276" satisfied condition "Succeeded or Failed"
Oct 13 14:17:52.856: INFO: Deleting pod "volume-prep-provisioning-2276" in namespace "provisioning-2276"
Oct 13 14:17:53.107: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-2276" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-4274
STEP: Checking for subpath error in container status
Oct 13 14:18:28.102: INFO: Deleting pod "pod-subpath-test-dynamicpv-4274" in namespace "provisioning-2276"
Oct 13 14:18:28.357: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4274" to be fully deleted
STEP: Deleting pod
Oct 13 14:18:28.602: INFO: Deleting pod "pod-subpath-test-dynamicpv-4274" in namespace "provisioning-2276"
STEP: Deleting pvc
Oct 13 14:18:29.337: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjh476"
... skipping 81 lines ...
Oct 13 14:18:35.943: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 14:18:37.261: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-022c47d5acab424fc".
Oct 13 14:18:37.261: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-zxjq
STEP: Creating a pod to test exec-volume-test
Oct 13 14:18:37.507: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-zxjq" in namespace "volume-6991" to be "Succeeded or Failed"
Oct 13 14:18:37.751: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 243.809417ms
Oct 13 14:18:39.999: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491440529s
Oct 13 14:18:42.244: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.73691582s
Oct 13 14:18:44.488: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.980546608s
Oct 13 14:18:46.732: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 9.224526426s
Oct 13 14:18:48.976: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.468876999s
Oct 13 14:18:51.221: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.71366867s
Oct 13 14:18:53.465: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.957521649s
Oct 13 14:18:55.711: INFO: Pod "exec-volume-test-inlinevolume-zxjq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.203428935s
STEP: Saw pod success
Oct 13 14:18:55.711: INFO: Pod "exec-volume-test-inlinevolume-zxjq" satisfied condition "Succeeded or Failed"
Oct 13 14:18:55.955: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-zxjq container exec-container-inlinevolume-zxjq: <nil>
STEP: delete the pod
Oct 13 14:18:56.521: INFO: Waiting for pod exec-volume-test-inlinevolume-zxjq to disappear
Oct 13 14:18:56.765: INFO: Pod exec-volume-test-inlinevolume-zxjq no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-zxjq
Oct 13 14:18:56.765: INFO: Deleting pod "exec-volume-test-inlinevolume-zxjq" in namespace "volume-6991"
Oct 13 14:18:57.334: INFO: Couldn't delete PD "aws://ap-south-1a/vol-022c47d5acab424fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022c47d5acab424fc is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 8120fad2-0714-4553-a321-f03994ac8851
Oct 13 14:19:03.431: INFO: Successfully deleted PD "aws://ap-south-1a/vol-022c47d5acab424fc".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:19:03.431: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6991" for this suite.
... skipping 70 lines ...
Oct 13 14:18:32.798: INFO: Creating resource for dynamic PV
Oct 13 14:18:32.798: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8113-e2e-sc86z2w
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 14:18:33.521: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 14:18:33.997: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:36.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:38.475: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:40.475: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:42.477: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:44.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:46.479: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:48.475: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:50.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:52.473: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:54.479: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:56.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:18:58.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:19:00.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:19:02.474: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:19:04.475: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8113-e2e-sc86z2w",
  	... // 3 identical fields
  }

Oct 13 14:19:04.955: INFO: Error updating pvc ebs.csi.aws.com6j6zr: PersistentVolumeClaim "ebs.csi.aws.com6j6zr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 220 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 85 lines ...
STEP: Deleting pod hostexec-ip-172-20-38-167.ap-south-1.compute.internal-kjgcs in namespace volumemode-6473
Oct 13 14:19:02.960: INFO: Deleting pod "pod-c3c71bd1-3a81-4e0b-970a-e4c5ca8f148e" in namespace "volumemode-6473"
Oct 13 14:19:03.211: INFO: Wait up to 5m0s for pod "pod-c3c71bd1-3a81-4e0b-970a-e4c5ca8f148e" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 14:19:05.703: INFO: Deleting PersistentVolumeClaim "pvc-gmx2f"
Oct 13 14:19:05.948: INFO: Deleting PersistentVolume "aws-v4dv5"
Oct 13 14:19:06.542: INFO: Couldn't delete PD "aws://ap-south-1a/vol-06312024dbf74491e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06312024dbf74491e is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 6074f485-33d2-41d2-b0f7-445424776c58
Oct 13 14:19:12.663: INFO: Couldn't delete PD "aws://ap-south-1a/vol-06312024dbf74491e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06312024dbf74491e is currently attached to i-03470a764f7e3fca5
	status code: 400, request id: 5c62fb27-108d-44dd-bf92-0186603b857f
Oct 13 14:19:18.822: INFO: Successfully deleted PD "aws://ap-south-1a/vol-06312024dbf74491e".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:19:18.822: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6473" for this suite.
... skipping 64 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 138 lines ...
Oct 13 14:18:34.487: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6100vcdvp
STEP: creating a claim
Oct 13 14:18:34.725: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nd9x
STEP: Creating a pod to test subpath
Oct 13 14:18:35.446: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nd9x" in namespace "provisioning-6100" to be "Succeeded or Failed"
Oct 13 14:18:35.685: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 238.126763ms
Oct 13 14:18:37.923: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476635102s
Oct 13 14:18:40.163: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.716661596s
Oct 13 14:18:42.406: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.959294571s
Oct 13 14:18:44.646: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 9.199406953s
Oct 13 14:18:46.885: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 11.438493844s
Oct 13 14:18:49.124: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 13.677187011s
Oct 13 14:18:51.362: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 15.915834985s
Oct 13 14:18:53.601: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 18.15459816s
Oct 13 14:18:55.841: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 20.394464349s
Oct 13 14:18:58.081: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Pending", Reason="", readiness=false. Elapsed: 22.634184161s
Oct 13 14:19:00.324: INFO: Pod "pod-subpath-test-dynamicpv-nd9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.877600732s
STEP: Saw pod success
Oct 13 14:19:00.324: INFO: Pod "pod-subpath-test-dynamicpv-nd9x" satisfied condition "Succeeded or Failed"
Oct 13 14:19:00.574: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-nd9x container test-container-volume-dynamicpv-nd9x: <nil>
STEP: delete the pod
Oct 13 14:19:01.063: INFO: Waiting for pod pod-subpath-test-dynamicpv-nd9x to disappear
Oct 13 14:19:01.301: INFO: Pod pod-subpath-test-dynamicpv-nd9x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nd9x
Oct 13 14:19:01.301: INFO: Deleting pod "pod-subpath-test-dynamicpv-nd9x" in namespace "provisioning-6100"
... skipping 62 lines ...
Oct 13 14:18:47.450: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 14:18:48.667: INFO: Successfully created a new PD: "aws://ap-south-1a/vol-0dc09698a1a3deffb".
Oct 13 14:18:48.668: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-9fdg
STEP: Creating a pod to test exec-volume-test
Oct 13 14:18:48.914: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-9fdg" in namespace "volume-8773" to be "Succeeded or Failed"
Oct 13 14:18:49.153: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Pending", Reason="", readiness=false. Elapsed: 238.899485ms
Oct 13 14:18:51.391: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.477009853s
Oct 13 14:18:53.629: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.715626524s
Oct 13 14:18:55.869: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.955160223s
Oct 13 14:18:58.107: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Pending", Reason="", readiness=false. Elapsed: 9.193215418s
Oct 13 14:19:00.346: INFO: Pod "exec-volume-test-inlinevolume-9fdg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.432473772s
STEP: Saw pod success
Oct 13 14:19:00.346: INFO: Pod "exec-volume-test-inlinevolume-9fdg" satisfied condition "Succeeded or Failed"
Oct 13 14:19:00.585: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod exec-volume-test-inlinevolume-9fdg container exec-container-inlinevolume-9fdg: <nil>
STEP: delete the pod
Oct 13 14:19:01.073: INFO: Waiting for pod exec-volume-test-inlinevolume-9fdg to disappear
Oct 13 14:19:01.311: INFO: Pod exec-volume-test-inlinevolume-9fdg no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-9fdg
Oct 13 14:19:01.311: INFO: Deleting pod "exec-volume-test-inlinevolume-9fdg" in namespace "volume-8773"
Oct 13 14:19:01.879: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0dc09698a1a3deffb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc09698a1a3deffb is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 85424b28-f620-4cb3-a46e-3f19fe6e03a8
Oct 13 14:19:07.958: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0dc09698a1a3deffb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc09698a1a3deffb is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 7e9bc4e7-ecf6-4493-aa4d-b7ddff485c82
Oct 13 14:19:14.055: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0dc09698a1a3deffb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc09698a1a3deffb is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 643fe795-cc64-4679-9830-7e007bc9cd04
Oct 13 14:19:20.149: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0dc09698a1a3deffb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc09698a1a3deffb is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 49b3c8bc-1694-499b-8d3b-8a0c67db1acb
Oct 13 14:19:26.257: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0dc09698a1a3deffb".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:19:26.257: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8773" for this suite.
... skipping 162 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 476 lines ...
Oct 13 14:18:56.746: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6679-e2e-scldlp6
STEP: creating a claim
Oct 13 14:18:56.993: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-r66c
STEP: Creating a pod to test exec-volume-test
Oct 13 14:18:57.738: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-r66c" in namespace "volume-6679" to be "Succeeded or Failed"
Oct 13 14:18:57.984: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 245.501528ms
Oct 13 14:19:00.229: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491046241s
Oct 13 14:19:02.476: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.73764373s
Oct 13 14:19:04.724: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.985839819s
Oct 13 14:19:06.970: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 9.231270263s
Oct 13 14:19:09.215: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 11.476790463s
Oct 13 14:19:11.462: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 13.723518589s
Oct 13 14:19:13.708: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 15.970106125s
Oct 13 14:19:15.954: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.215874663s
Oct 13 14:19:18.201: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.462244776s
Oct 13 14:19:20.446: INFO: Pod "exec-volume-test-dynamicpv-r66c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.708161593s
STEP: Saw pod success
Oct 13 14:19:20.447: INFO: Pod "exec-volume-test-dynamicpv-r66c" satisfied condition "Succeeded or Failed"
Oct 13 14:19:20.693: INFO: Trying to get logs from node ip-172-20-38-167.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-r66c container exec-container-dynamicpv-r66c: <nil>
STEP: delete the pod
Oct 13 14:19:21.194: INFO: Waiting for pod exec-volume-test-dynamicpv-r66c to disappear
Oct 13 14:19:21.439: INFO: Pod exec-volume-test-dynamicpv-r66c no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-r66c
Oct 13 14:19:21.439: INFO: Deleting pod "exec-volume-test-dynamicpv-r66c" in namespace "volume-6679"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 427 lines ...
Oct 13 14:19:37.283: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-619v7sb8
STEP: creating a claim
Oct 13 14:19:37.522: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5fhq
STEP: Creating a pod to test exec-volume-test
Oct 13 14:19:38.281: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5fhq" in namespace "volume-619" to be "Succeeded or Failed"
Oct 13 14:19:38.519: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 237.94511ms
Oct 13 14:19:40.758: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.476993072s
Oct 13 14:19:42.997: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.716038773s
Oct 13 14:19:45.237: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.956475882s
Oct 13 14:19:47.475: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 9.19428235s
Oct 13 14:19:49.714: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.433497259s
Oct 13 14:19:51.953: INFO: Pod "exec-volume-test-dynamicpv-5fhq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.672199374s
STEP: Saw pod success
Oct 13 14:19:51.953: INFO: Pod "exec-volume-test-dynamicpv-5fhq" satisfied condition "Succeeded or Failed"
Oct 13 14:19:52.191: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-5fhq container exec-container-dynamicpv-5fhq: <nil>
STEP: delete the pod
Oct 13 14:19:52.675: INFO: Waiting for pod exec-volume-test-dynamicpv-5fhq to disappear
Oct 13 14:19:52.913: INFO: Pod exec-volume-test-dynamicpv-5fhq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5fhq
Oct 13 14:19:52.913: INFO: Deleting pod "exec-volume-test-dynamicpv-5fhq" in namespace "volume-619"
... skipping 125 lines ...
Oct 13 14:18:22.841: INFO: Creating resource for dynamic PV
Oct 13 14:18:22.841: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4604skp5
STEP: creating a claim
Oct 13 14:18:23.086: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-460
Oct 13 14:18:23.824: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-460" in namespace "provisioning-460" to be "Succeeded or Failed"
Oct 13 14:18:24.070: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 245.985095ms
Oct 13 14:18:26.315: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491009647s
Oct 13 14:18:28.562: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 4.73854025s
Oct 13 14:18:30.808: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 6.984348005s
Oct 13 14:18:33.054: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 9.23048358s
Oct 13 14:18:35.299: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 11.475805768s
Oct 13 14:18:37.545: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 13.721203565s
Oct 13 14:18:39.792: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 15.967979159s
Oct 13 14:18:42.037: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 18.213465189s
Oct 13 14:18:44.283: INFO: Pod "volume-prep-provisioning-460": Phase="Pending", Reason="", readiness=false. Elapsed: 20.45952304s
Oct 13 14:18:46.532: INFO: Pod "volume-prep-provisioning-460": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.708089756s
STEP: Saw pod success
Oct 13 14:18:46.532: INFO: Pod "volume-prep-provisioning-460" satisfied condition "Succeeded or Failed"
Oct 13 14:18:46.532: INFO: Deleting pod "volume-prep-provisioning-460" in namespace "provisioning-460"
Oct 13 14:18:46.782: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-460" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ffsz
STEP: Checking for subpath error in container status
Oct 13 14:19:53.763: INFO: Deleting pod "pod-subpath-test-dynamicpv-ffsz" in namespace "provisioning-460"
Oct 13 14:19:54.013: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ffsz" to be fully deleted
STEP: Deleting pod
Oct 13 14:19:54.258: INFO: Deleting pod "pod-subpath-test-dynamicpv-ffsz" in namespace "provisioning-460"
STEP: Deleting pvc
Oct 13 14:19:54.993: INFO: Deleting PersistentVolumeClaim "awswkqmb"
... skipping 30 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 127 lines ...
Oct 13 14:20:03.831: INFO: PersistentVolumeClaim pvc-gn28q found but phase is Pending instead of Bound.
Oct 13 14:20:06.076: INFO: PersistentVolumeClaim pvc-gn28q found and phase=Bound (6.976507626s)
Oct 13 14:20:06.076: INFO: Waiting up to 3m0s for PersistentVolume aws-4zxgn to have phase Bound
Oct 13 14:20:06.327: INFO: PersistentVolume aws-4zxgn found and phase=Bound (251.378658ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-dqj2
STEP: Creating a pod to test exec-volume-test
Oct 13 14:20:07.069: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-dqj2" in namespace "volume-9983" to be "Succeeded or Failed"
Oct 13 14:20:07.312: INFO: Pod "exec-volume-test-preprovisionedpv-dqj2": Phase="Pending", Reason="", readiness=false. Elapsed: 243.174043ms
Oct 13 14:20:09.556: INFO: Pod "exec-volume-test-preprovisionedpv-dqj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.487041402s
Oct 13 14:20:11.800: INFO: Pod "exec-volume-test-preprovisionedpv-dqj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.731049114s
Oct 13 14:20:14.046: INFO: Pod "exec-volume-test-preprovisionedpv-dqj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.977500252s
STEP: Saw pod success
Oct 13 14:20:14.046: INFO: Pod "exec-volume-test-preprovisionedpv-dqj2" satisfied condition "Succeeded or Failed"
Oct 13 14:20:14.294: INFO: Trying to get logs from node ip-172-20-54-148.ap-south-1.compute.internal pod exec-volume-test-preprovisionedpv-dqj2 container exec-container-preprovisionedpv-dqj2: <nil>
STEP: delete the pod
Oct 13 14:20:14.799: INFO: Waiting for pod exec-volume-test-preprovisionedpv-dqj2 to disappear
Oct 13 14:20:15.050: INFO: Pod exec-volume-test-preprovisionedpv-dqj2 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-dqj2
Oct 13 14:20:15.050: INFO: Deleting pod "exec-volume-test-preprovisionedpv-dqj2" in namespace "volume-9983"
STEP: Deleting pv and pvc
Oct 13 14:20:15.293: INFO: Deleting PersistentVolumeClaim "pvc-gn28q"
Oct 13 14:20:15.539: INFO: Deleting PersistentVolume "aws-4zxgn"
Oct 13 14:20:16.138: INFO: Couldn't delete PD "aws://ap-south-1a/vol-0e985cbfdaeb8be15", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e985cbfdaeb8be15 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 0f81b050-b39b-4afe-a37a-2eb78ee0dada
Oct 13 14:20:22.265: INFO: Successfully deleted PD "aws://ap-south-1a/vol-0e985cbfdaeb8be15".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:20:22.265: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9983" for this suite.
... skipping 181 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 166 lines ...
Oct 13 14:19:34.042: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7847-e2e-scjt5br
STEP: creating a claim
Oct 13 14:19:34.288: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gtx5
STEP: Creating a pod to test subpath
Oct 13 14:19:35.029: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gtx5" in namespace "provisioning-7847" to be "Succeeded or Failed"
Oct 13 14:19:35.274: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 245.208773ms
Oct 13 14:19:37.520: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491475453s
Oct 13 14:19:39.767: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.738056423s
Oct 13 14:19:42.013: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.983817811s
Oct 13 14:19:44.259: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.230481543s
Oct 13 14:19:46.506: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.476661346s
Oct 13 14:19:48.752: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.722501375s
Oct 13 14:19:50.997: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 15.967630849s
Oct 13 14:19:53.243: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.213860634s
Oct 13 14:19:55.489: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.459659746s
Oct 13 14:19:57.736: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.707014017s
Oct 13 14:20:00.015: INFO: Pod "pod-subpath-test-dynamicpv-gtx5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.985610292s
STEP: Saw pod success
Oct 13 14:20:00.015: INFO: Pod "pod-subpath-test-dynamicpv-gtx5" satisfied condition "Succeeded or Failed"
Oct 13 14:20:00.260: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-gtx5 container test-container-volume-dynamicpv-gtx5: <nil>
STEP: delete the pod
Oct 13 14:20:00.796: INFO: Waiting for pod pod-subpath-test-dynamicpv-gtx5 to disappear
Oct 13 14:20:01.041: INFO: Pod pod-subpath-test-dynamicpv-gtx5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gtx5
Oct 13 14:20:01.041: INFO: Deleting pod "pod-subpath-test-dynamicpv-gtx5" in namespace "provisioning-7847"
... skipping 162 lines ...
Oct 13 14:20:34.961: INFO: Waiting for pod aws-client to disappear
Oct 13 14:20:35.201: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 14:20:35.201: INFO: Deleting PersistentVolumeClaim "pvc-hsv5r"
Oct 13 14:20:35.443: INFO: Deleting PersistentVolume "aws-4rbb5"
Oct 13 14:20:36.789: INFO: Couldn't delete PD "aws://ap-south-1a/vol-00d3f1185bcd3dbe4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d3f1185bcd3dbe4 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 20bdb8fb-4601-41a2-bca8-3f84256a1383
Oct 13 14:20:42.905: INFO: Couldn't delete PD "aws://ap-south-1a/vol-00d3f1185bcd3dbe4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d3f1185bcd3dbe4 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: 7873ea70-71eb-4b14-bda9-54c6d51c10d9
Oct 13 14:20:49.000: INFO: Successfully deleted PD "aws://ap-south-1a/vol-00d3f1185bcd3dbe4".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:20:49.000: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4147" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:20:12.598: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 14:20:13.800: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:20:13.800: INFO: Creating resource for dynamic PV
Oct 13 14:20:13.800: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2942t4bld
STEP: creating a claim
Oct 13 14:20:14.041: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gvx4
STEP: Checking for subpath error in container status
Oct 13 14:20:31.258: INFO: Deleting pod "pod-subpath-test-dynamicpv-gvx4" in namespace "provisioning-2942"
Oct 13 14:20:31.498: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gvx4" to be fully deleted
STEP: Deleting pod
Oct 13 14:20:33.979: INFO: Deleting pod "pod-subpath-test-dynamicpv-gvx4" in namespace "provisioning-2942"
STEP: Deleting pvc
Oct 13 14:20:34.696: INFO: Deleting PersistentVolumeClaim "awslxvm4"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:20:51.630: INFO: >>> kubeConfig: /root/.kube/config
... skipping 189 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 357 lines ...
STEP: Deleting pod aws-client in namespace volume-9538
Oct 13 14:20:59.278: INFO: Waiting for pod aws-client to disappear
Oct 13 14:20:59.523: INFO: Pod aws-client still exists
Oct 13 14:21:01.523: INFO: Waiting for pod aws-client to disappear
Oct 13 14:21:01.769: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 14:21:02.128: INFO: Couldn't delete PD "aws://ap-south-1a/vol-071cdf810dc715363", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-071cdf810dc715363 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: d858fd42-a781-4b86-a73f-0edfb2fe7797
Oct 13 14:21:08.241: INFO: Couldn't delete PD "aws://ap-south-1a/vol-071cdf810dc715363", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-071cdf810dc715363 is currently attached to i-017d51d778c8d1bd9
	status code: 400, request id: b476b74c-3b97-430a-bc30-161b9716144f
Oct 13 14:21:14.342: INFO: Successfully deleted PD "aws://ap-south-1a/vol-071cdf810dc715363".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 14:21:14.342: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9538" for this suite.
... skipping 87 lines ...
Oct 13 14:20:20.688: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3447sjtfg
STEP: creating a claim
Oct 13 14:20:20.935: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hwd5
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 14:20:21.676: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hwd5" in namespace "provisioning-3447" to be "Succeeded or Failed"
Oct 13 14:20:21.921: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 244.763416ms
Oct 13 14:20:24.166: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.490206981s
Oct 13 14:20:26.413: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.736867757s
Oct 13 14:20:28.659: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.983284764s
Oct 13 14:20:30.905: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.228930986s
Oct 13 14:20:33.151: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.47476176s
... skipping 5 lines ...
Oct 13 14:20:46.625: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Running", Reason="", readiness=true. Elapsed: 24.949474064s
Oct 13 14:20:48.871: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Running", Reason="", readiness=true. Elapsed: 27.195192109s
Oct 13 14:20:51.117: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Running", Reason="", readiness=true. Elapsed: 29.44143324s
Oct 13 14:20:53.364: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Running", Reason="", readiness=true. Elapsed: 31.688435157s
Oct 13 14:20:55.610: INFO: Pod "pod-subpath-test-dynamicpv-hwd5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.934611814s
STEP: Saw pod success
Oct 13 14:20:55.610: INFO: Pod "pod-subpath-test-dynamicpv-hwd5" satisfied condition "Succeeded or Failed"
Oct 13 14:20:55.858: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-hwd5 container test-container-subpath-dynamicpv-hwd5: <nil>
STEP: delete the pod
Oct 13 14:20:56.374: INFO: Waiting for pod pod-subpath-test-dynamicpv-hwd5 to disappear
Oct 13 14:20:56.622: INFO: Pod pod-subpath-test-dynamicpv-hwd5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hwd5
Oct 13 14:20:56.622: INFO: Deleting pod "pod-subpath-test-dynamicpv-hwd5" in namespace "provisioning-3447"
... skipping 39 lines ...
Oct 13 14:20:36.643: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8818n2vl
STEP: creating a claim
Oct 13 14:20:36.883: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-c9q2
STEP: Creating a pod to test subpath
Oct 13 14:20:37.609: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-c9q2" in namespace "provisioning-881" to be "Succeeded or Failed"
Oct 13 14:20:37.849: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 239.851158ms
Oct 13 14:20:40.089: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.4798051s
Oct 13 14:20:42.329: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.720236171s
Oct 13 14:20:44.570: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.960851393s
Oct 13 14:20:46.809: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.20011291s
Oct 13 14:20:49.053: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.444569534s
Oct 13 14:20:51.294: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.685018963s
Oct 13 14:20:53.534: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.925058371s
Oct 13 14:20:55.773: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.164512906s
Oct 13 14:20:58.013: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.404224748s
Oct 13 14:21:00.257: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.648555728s
Oct 13 14:21:02.501: INFO: Pod "pod-subpath-test-dynamicpv-c9q2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.892256296s
STEP: Saw pod success
Oct 13 14:21:02.501: INFO: Pod "pod-subpath-test-dynamicpv-c9q2" satisfied condition "Succeeded or Failed"
Oct 13 14:21:02.741: INFO: Trying to get logs from node ip-172-20-55-40.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-c9q2 container test-container-subpath-dynamicpv-c9q2: <nil>
STEP: delete the pod
Oct 13 14:21:03.231: INFO: Waiting for pod pod-subpath-test-dynamicpv-c9q2 to disappear
Oct 13 14:21:03.470: INFO: Pod pod-subpath-test-dynamicpv-c9q2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-c9q2
Oct 13 14:21:03.470: INFO: Deleting pod "pod-subpath-test-dynamicpv-c9q2" in namespace "provisioning-881"
... skipping 63 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.GBEnirwJi/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.GBEnirwJi/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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 225 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:21:09.111: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 14:21:10.329: INFO: Creating resource for dynamic PV
Oct 13 14:21:10.329: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1188-e2e-sct956w
STEP: creating a claim
Oct 13 14:21:10.574: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gbkt
STEP: Checking for subpath error in container status
Oct 13 14:21:27.798: INFO: Deleting pod "pod-subpath-test-dynamicpv-gbkt" in namespace "provisioning-1188"
Oct 13 14:21:28.050: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gbkt" to be fully deleted
STEP: Deleting pod
Oct 13 14:21:30.542: INFO: Deleting pod "pod-subpath-test-dynamicpv-gbkt" in namespace "provisioning-1188"
STEP: Deleting pvc
Oct 13 14:21:31.272: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comn78b7"
... skipping 11 lines ...

• [SLOW TEST:39.128 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 82 lines ...
Oct 13 14:21:19.750: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4465-e2e-sc5z85f
STEP: creating a claim
Oct 13 14:21:19.989: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8mwk
STEP: Creating a pod to test exec-volume-test
Oct 13 14:21:20.703: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8mwk" in namespace "volume-4465" to be "Succeeded or Failed"
Oct 13 14:21:20.941: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 237.059054ms
Oct 13 14:21:23.178: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.474443763s
Oct 13 14:21:25.417: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.713244092s
Oct 13 14:21:27.655: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.9510876s
Oct 13 14:21:29.893: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 9.189941636s
Oct 13 14:21:32.132: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 11.428630212s
Oct 13 14:21:34.370: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.666174475s
Oct 13 14:21:36.608: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Pending", Reason="", readiness=false. Elapsed: 15.904245485s
Oct 13 14:21:38.846: INFO: Pod "exec-volume-test-dynamicpv-8mwk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.142537414s
STEP: Saw pod success
Oct 13 14:21:38.846: INFO: Pod "exec-volume-test-dynamicpv-8mwk" satisfied condition "Succeeded or Failed"
Oct 13 14:21:39.083: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod exec-volume-test-dynamicpv-8mwk container exec-container-dynamicpv-8mwk: <nil>
STEP: delete the pod
Oct 13 14:21:39.566: INFO: Waiting for pod exec-volume-test-dynamicpv-8mwk to disappear
Oct 13 14:21:39.802: INFO: Pod exec-volume-test-dynamicpv-8mwk no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8mwk
Oct 13 14:21:39.802: INFO: Deleting pod "exec-volume-test-dynamicpv-8mwk" in namespace "volume-4465"
... skipping 34 lines ...
Oct 13 14:20:37.703: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9434-e2e-scvhcqb      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-9434    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-9434-e2e-scvhcqb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9434    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-9434-e2e-scvhcqb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9434    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-9434-e2e-scvhcqb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9434-e2e-scvhcqb    5b83a4ff-3a2e-47b9-b563-2b66a420beab 13655 0 2021-10-13 14:20:38 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 14:20:38 +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-4lh7r pvc- provisioning-9434  e7548547-7ffb-4675-9fc1-37265a14d228 13672 0 2021-10-13 14:20:38 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 14:20:38 +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-9434-e2e-scvhcqb,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-892bfb29-e5b3-4036-bbdc-cd5fec771ad5 in namespace provisioning-9434
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 14:21:04.418: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-9bxt8" in namespace "provisioning-9434" to be "Succeeded or Failed"
Oct 13 14:21:04.663: INFO: Pod "pvc-volume-tester-writer-9bxt8": Phase="Pending", Reason="", readiness=false. Elapsed: 244.899902ms
Oct 13 14:21:06.908: INFO: Pod "pvc-volume-tester-writer-9bxt8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.490868411s
STEP: Saw pod success
Oct 13 14:21:06.909: INFO: Pod "pvc-volume-tester-writer-9bxt8" satisfied condition "Succeeded or Failed"
Oct 13 14:21:07.406: INFO: Pod pvc-volume-tester-writer-9bxt8 has the following logs: 
Oct 13 14:21:07.407: INFO: Deleting pod "pvc-volume-tester-writer-9bxt8" in namespace "provisioning-9434"
Oct 13 14:21:07.685: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-9bxt8" 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-55-40.ap-south-1.compute.internal"
Oct 13 14:21:08.673: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-t9cn8" in namespace "provisioning-9434" to be "Succeeded or Failed"
Oct 13 14:21:08.918: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 245.150887ms
Oct 13 14:21:11.164: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.491421138s
Oct 13 14:21:13.412: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.739194578s
Oct 13 14:21:15.659: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.985635109s
Oct 13 14:21:17.905: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 9.232440492s
Oct 13 14:21:20.153: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 11.480380711s
Oct 13 14:21:22.399: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.726099103s
Oct 13 14:21:24.645: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.972305177s
Oct 13 14:21:26.892: INFO: Pod "pvc-volume-tester-reader-t9cn8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.218940597s
STEP: Saw pod success
Oct 13 14:21:26.892: INFO: Pod "pvc-volume-tester-reader-t9cn8" satisfied condition "Succeeded or Failed"
Oct 13 14:21:27.395: INFO: Pod pvc-volume-tester-reader-t9cn8 has the following logs: hello world

Oct 13 14:21:27.395: INFO: Deleting pod "pvc-volume-tester-reader-t9cn8" in namespace "provisioning-9434"
Oct 13 14:21:27.652: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-t9cn8" to be fully deleted
Oct 13 14:21:27.898: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-4lh7r] to have phase Bound
Oct 13 14:21:28.143: INFO: PersistentVolumeClaim pvc-4lh7r found and phase=Bound (244.929106ms)
... skipping 247 lines ...
Oct 13 14:20:57.560: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7333sdp5v
STEP: creating a claim
Oct 13 14:20:57.806: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-459c
STEP: Creating a pod to test subpath
Oct 13 14:20:58.547: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-459c" in namespace "provisioning-7333" to be "Succeeded or Failed"
Oct 13 14:20:58.791: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 243.00897ms
Oct 13 14:21:01.035: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.487280808s
Oct 13 14:21:03.279: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.731632245s
Oct 13 14:21:05.525: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.977942668s
Oct 13 14:21:07.781: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 9.233559704s
Oct 13 14:21:10.026: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 11.478601539s
... skipping 8 lines ...
Oct 13 14:21:30.233: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 31.68531652s
Oct 13 14:21:32.478: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 33.930300463s
Oct 13 14:21:34.722: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 36.17429576s
Oct 13 14:21:36.967: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Pending", Reason="", readiness=false. Elapsed: 38.419639128s
Oct 13 14:21:39.212: INFO: Pod "pod-subpath-test-dynamicpv-459c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.664702195s
STEP: Saw pod success
Oct 13 14:21:39.212: INFO: Pod "pod-subpath-test-dynamicpv-459c" satisfied condition "Succeeded or Failed"
Oct 13 14:21:39.457: INFO: Trying to get logs from node ip-172-20-57-186.ap-south-1.compute.internal pod pod-subpath-test-dynamicpv-459c container test-container-subpath-dynamicpv-459c: <nil>
STEP: delete the pod
Oct 13 14:21:39.958: INFO: Waiting for pod pod-subpath-test-dynamicpv-459c to disappear
Oct 13 14:21:40.202: INFO: Pod pod-subpath-test-dynamicpv-459c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-459c
Oct 13 14:21:40.202: INFO: Deleting pod "pod-subpath-test-dynamicpv-459c" in namespace "provisioning-7333"
... skipping 800 lines ...
STEP: Found 9 events.
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:16:41 +0000 UTC - event for pvc-4mtxn: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:16:41 +0000 UTC - event for pvc-4mtxn: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } Provisioning: External provisioner is provisioning volume for claim "topology-4754/pvc-4mtxn"
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:16:42 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {default-scheduler } FailedScheduling: 0/5 nodes are available: 5 pod has unbound immediate PersistentVolumeClaims.
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:16:45 +0000 UTC - event for pvc-4mtxn: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } ProvisioningSucceeded: Successfully provisioned volume pvc-13b7edc0-4c90-4430-b3b9-8bf4a46dd694
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:16:46 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {default-scheduler } Scheduled: Successfully assigned topology-4754/pod-e46eea6a-a388-47a4-85f3-b18633301b58 to ip-172-20-54-148.ap-south-1.compute.internal
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:17:36 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-13b7edc0-4c90-4430-b3b9-8bf4a46dd694" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:17:46 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-13b7edc0-4c90-4430-b3b9-8bf4a46dd694" : rpc error: code = Internal desc = Could not attach volume "vol-014a312bac1f50d36" to node "i-0eaf0df9fd5dd565c": attachment of disk "vol-014a312bac1f50d36" failed, expected device to be attached but was attaching
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:18:49 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-kqwsc volume1]: timed out waiting for the condition
Oct 13 14:23:32.448: INFO: At 2021-10-13 14:21:06 +0000 UTC - event for pod-e46eea6a-a388-47a4-85f3-b18633301b58: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-kqwsc]: timed out waiting for the condition
Oct 13 14:23:32.687: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 13 14:23:32.687: INFO: 
Oct 13 14:23:32.928: INFO: 
Logging node info for node ip-172-20-38-167.ap-south-1.compute.internal
... skipping 162 lines ...
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should provision a volume and schedule a pod with AllowedTopologies [It]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:164

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

... skipping 116 lines ...
Oct 13 14:23:37.288: INFO: Waiting for pod aws-injector to disappear
Oct 13 14:23:37.533: INFO: Pod aws-injector still exists
Oct 13 14:23:39.287: INFO: Waiting for pod aws-injector to disappear
Oct 13 14:23:39.533: INFO: Pod aws-injector still exists
Oct 13 14:23:41.287: INFO: Waiting for pod aws-injector to disappear
Oct 13 14:23:41.533: INFO: Pod aws-injector no longer exists
Oct 13 14:23:41.533: FAIL: Failed to create injector pod: timed out waiting for the condition

Full Stack Trace
k8s.io/kubernetes/test/e2e/storage/testsuites.(*volumesTestSuite).DefineTests.func3()
	/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186 +0x438
github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes.TestEBSCSI(0x407c59)
	/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:82 +0x319
testing.tRunner(0xc0003096c0, 0x28f9180)
	/usr/local/go/src/testing/testing.go:1259 +0x102
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1306 +0x35a
STEP: cleaning the environment after aws
Oct 13 14:23:42.669: INFO: Couldn't delete PD "aws://ap-south-1a/vol-015256f5ccd7d00c8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015256f5ccd7d00c8 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: 8acc344a-04b5-4f80-bc93-3b613b658ef5
Oct 13 14:23:48.785: INFO: Couldn't delete PD "aws://ap-south-1a/vol-015256f5ccd7d00c8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015256f5ccd7d00c8 is currently attached to i-0eaf0df9fd5dd565c
	status code: 400, request id: f696869b-a1b2-4729-a513-49349240ee2c
Oct 13 14:23:54.898: INFO: Successfully deleted PD "aws://ap-south-1a/vol-015256f5ccd7d00c8".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
STEP: Collecting events from namespace "volume-1583".
STEP: Found 4 events.
Oct 13 14:23:55.144: INFO: At 2021-10-13 14:16:57 +0000 UTC - event for aws-injector: {default-scheduler } Scheduled: Successfully assigned volume-1583/aws-injector to ip-172-20-54-148.ap-south-1.compute.internal
Oct 13 14:23:55.144: INFO: At 2021-10-13 14:17:39 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-015256f5ccd7d00c8" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 13 14:23:55.144: INFO: At 2021-10-13 14:17:49 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-015256f5ccd7d00c8" : rpc error: code = Internal desc = Could not attach volume "vol-015256f5ccd7d00c8" to node "i-0eaf0df9fd5dd565c": attachment of disk "vol-015256f5ccd7d00c8" failed, expected device to be attached but was attaching
Oct 13 14:23:55.144: INFO: At 2021-10-13 14:19:00 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[aws-volume-0 kube-api-access-kpsgm]: timed out waiting for the condition
Oct 13 14:23:55.390: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 13 14:23:55.390: INFO: 
Oct 13 14:23:55.636: INFO: 
Logging node info for node ip-172-20-38-167.ap-south-1.compute.internal
Oct 13 14:23:55.882: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-38-167.ap-south-1.compute.internal    63630aab-5b6e-48ed-a1b7-38e5588ff889 15657 0 2021-10-13 14:09:08 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-south-1 failure-domain.beta.kubernetes.io/zone:ap-south-1a kops.k8s.io/instancegroup:nodes-ap-south-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-38-167.ap-south-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ap-south-1a topology.kubernetes.io/region:ap-south-1 topology.kubernetes.io/zone:ap-south-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-03470a764f7e3fca5"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.38.167/19 projectcalico.org/IPv4IPIPTunnelAddr:100.103.154.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-10-13 14:09:08 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-10-13 14:09:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {kube-controller-manager Update v1 2021-10-13 14:09:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.4.0/24\"":{}}}}} {calico-node Update v1 2021-10-13 14:09:32 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-10-13 14:22:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.4.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-south-1a/i-03470a764f7e3fca5,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059734016 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954876416 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-10-13 14:09:32 +0000 UTC,LastTransitionTime:2021-10-13 14:09:32 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:18 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.38.167,},NodeAddress{Type:ExternalIP,Address:13.233.110.223,},NodeAddress{Type:Hostname,Address:ip-172-20-38-167.ap-south-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-38-167.ap-south-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-13-233-110-223.ap-south-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2740bef6759551d43c09c1c2c7bb7a,SystemUUID:ec2740be-f675-9551-d43c-09c1c2c7bb7a,BootID:40edda2a-0920-4e7e-90b9-2885e64bc86d,KernelVersion:5.11.0-1019-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.11,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:5c03401df9e8fa384b66efc8bfd954a0371ad584a9430eca7d4d9338654d7fe0 k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.4.0],SizeBytes:116606616,},ContainerImage{Names:[docker.io/calico/node@sha256:1ae8f57edec7c3a84cd48dd94132a1dcfd7c61bfff819c559f9379d4a56fe3b1 docker.io/calico/node:v3.20.2],SizeBytes:57637498,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:3dae26de7388ff3c124b9abd7e8d12863887391f23549c4aebfbfa20cc0700a5 docker.io/calico/cni:v3.20.2],SizeBytes:48389252,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:4514cc1b2f7536fe1d514fad8a2c46103382243bb9db5ea2d0063fcd2001e8f7 docker.io/calico/pod2daemon-flexvol:v3.20.2],SizeBytes:9359081,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 156 lines ...
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (ext4)] volumes
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should store data [It]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:159

      Oct 13 14:23:41.534: Failed to create injector pod: timed out waiting for the condition

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 14:16:52.307: 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.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 14:16:53.512: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 14:16:53.512: INFO: Creating resource for dynamic PV
Oct 13 14:16:53.512: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4650vrjrl
STEP: creating a claim
Oct 13 14:16:53.761: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-clfc
STEP: Checking for subpath error in container status
Oct 13 14:21:55.215: INFO: Deleting pod "pod-subpath-test-dynamicpv-clfc" in namespace "provisioning-4650"
Oct 13 14:21:55.459: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-clfc" to be fully deleted
STEP: Deleting pod
Oct 13 14:23:41.943: INFO: Deleting pod "pod-subpath-test-dynamicpv-clfc" in namespace "provisioning-4650"
STEP: Deleting pvc
Oct 13 14:23:42.666: INFO: Deleting PersistentVolumeClaim "awst2ffh"
... skipping 10 lines ...
STEP: Found 8 events.
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:16:53 +0000 UTC - event for awst2ffh: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:16:54 +0000 UTC - event for awst2ffh: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:16:54 +0000 UTC - event for awst2ffh: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } Provisioning: External provisioner is provisioning volume for claim "provisioning-4650/awst2ffh"
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:16:57 +0000 UTC - event for awst2ffh: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } ProvisioningSucceeded: Successfully provisioned volume pvc-80c0bca3-7915-42db-99aa-944bcf622b9e
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:16:58 +0000 UTC - event for pod-subpath-test-dynamicpv-clfc: {default-scheduler } Scheduled: Successfully assigned provisioning-4650/pod-subpath-test-dynamicpv-clfc to ip-172-20-54-148.ap-south-1.compute.internal
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:17:40 +0000 UTC - event for pod-subpath-test-dynamicpv-clfc: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-80c0bca3-7915-42db-99aa-944bcf622b9e" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:17:49 +0000 UTC - event for pod-subpath-test-dynamicpv-clfc: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-80c0bca3-7915-42db-99aa-944bcf622b9e" : rpc error: code = Internal desc = Could not attach volume "vol-04b3c4d9f4bbf701e" to node "i-0eaf0df9fd5dd565c": attachment of disk "vol-04b3c4d9f4bbf701e" failed, expected device to be attached but was attaching
Oct 13 14:24:04.602: INFO: At 2021-10-13 14:19:01 +0000 UTC - event for pod-subpath-test-dynamicpv-clfc: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[test-volume], unattached volumes=[test-volume liveness-probe-volume kube-api-access-c48sj]: timed out waiting for the condition
Oct 13 14:24:04.843: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 13 14:24:04.843: INFO: 
Oct 13 14:24:05.090: INFO: 
Logging node info for node ip-172-20-38-167.ap-south-1.compute.internal
Oct 13 14:24:05.332: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-38-167.ap-south-1.compute.internal    63630aab-5b6e-48ed-a1b7-38e5588ff889 15657 0 2021-10-13 14:09:08 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-south-1 failure-domain.beta.kubernetes.io/zone:ap-south-1a kops.k8s.io/instancegroup:nodes-ap-south-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-38-167.ap-south-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ap-south-1a topology.kubernetes.io/region:ap-south-1 topology.kubernetes.io/zone:ap-south-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-03470a764f7e3fca5"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.38.167/19 projectcalico.org/IPv4IPIPTunnelAddr:100.103.154.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-10-13 14:09:08 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-10-13 14:09:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {kube-controller-manager Update v1 2021-10-13 14:09:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.4.0/24\"":{}}}}} {calico-node Update v1 2021-10-13 14:09:32 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-10-13 14:22:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.4.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-south-1a/i-03470a764f7e3fca5,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059734016 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954876416 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-10-13 14:09:32 +0000 UTC,LastTransitionTime:2021-10-13 14:09:32 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:08 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-10-13 14:22:30 +0000 UTC,LastTransitionTime:2021-10-13 14:09:18 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.38.167,},NodeAddress{Type:ExternalIP,Address:13.233.110.223,},NodeAddress{Type:Hostname,Address:ip-172-20-38-167.ap-south-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-38-167.ap-south-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-13-233-110-223.ap-south-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2740bef6759551d43c09c1c2c7bb7a,SystemUUID:ec2740be-f675-9551-d43c-09c1c2c7bb7a,BootID:40edda2a-0920-4e7e-90b9-2885e64bc86d,KernelVersion:5.11.0-1019-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.11,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:5c03401df9e8fa384b66efc8bfd954a0371ad584a9430eca7d4d9338654d7fe0 k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.4.0],SizeBytes:116606616,},ContainerImage{Names:[docker.io/calico/node@sha256:1ae8f57edec7c3a84cd48dd94132a1dcfd7c61bfff819c559f9379d4a56fe3b1 docker.io/calico/node:v3.20.2],SizeBytes:57637498,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:3dae26de7388ff3c124b9abd7e8d12863887391f23549c4aebfbfa20cc0700a5 docker.io/calico/cni:v3.20.2],SizeBytes:48389252,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:4514cc1b2f7536fe1d514fad8a2c46103382243bb9db5ea2d0063fcd2001e8f7 docker.io/calico/pod2daemon-flexvol:v3.20.2],SizeBytes:9359081,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 153 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GBEnirwJi/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [It]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      while waiting for subpath failure
      Unexpected error:
          <*errors.errorString | 0xc000821040>: {
              s: "error waiting for pod subpath error to occur: timed out waiting for the condition",
          }
          error waiting for pod subpath error to occur: timed out waiting for the condition
      occurred

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:713
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 94 lines ...
Oct 13 14:20:24.963: INFO: Deleting pod "inline-volume-f2rj5" in namespace "ephemeral-7577"
Oct 13 14:20:25.207: INFO: Wait up to 5m0s for pod "inline-volume-f2rj5" to be fully deleted
Oct 13 14:20:25.451: INFO: Creating resource for dynamic PV
Oct 13 14:20:25.451: INFO: Using claimSize:1Gi, test suite supported size:{ }, driver(aws) supported size:{ } 
STEP: creating a StorageClass ephemeral-75772fntc
STEP: checking the requested inline volume exists in the pod running on node {Name: Selector:map[] Affinity:nil}
Oct 13 14:35:26.941: INFO: Error getting logs for pod inline-volume-tester-9pzx6: the server rejected our request for an unknown reason (get pods inline-volume-tester-9pzx6)
Oct 13 14:35:27.671: INFO: Deleting pod "inline-volume-tester-9pzx6" in namespace "ephemeral-7577"
Oct 13 14:35:27.922: INFO: Wait up to 5m0s for pod "inline-volume-tester-9pzx6" to be fully deleted
Oct 13 14:36:12.409: INFO: Wait up to 5m0s for pod PV pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c to be fully deleted
Oct 13 14:36:12.409: INFO: Waiting up to 5m0s for PersistentVolume pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c to get deleted
Oct 13 14:36:12.653: INFO: PersistentVolume pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c found and phase=Released (243.533949ms)
Oct 13 14:36:17.896: INFO: PersistentVolume pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c found and phase=Released (5.487210504s)
... skipping 17 lines ...
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:27 +0000 UTC - event for inline-volume-tester-9pzx6-my-volume-0: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } Provisioning: External provisioner is provisioning volume for claim "ephemeral-7577/inline-volume-tester-9pzx6-my-volume-0"
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:27 +0000 UTC - event for inline-volume-tester-9pzx6-my-volume-1: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:27 +0000 UTC - event for inline-volume-tester-9pzx6-my-volume-1: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } Provisioning: External provisioner is provisioning volume for claim "ephemeral-7577/inline-volume-tester-9pzx6-my-volume-1"
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:30 +0000 UTC - event for inline-volume-tester-9pzx6-my-volume-0: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } ProvisioningSucceeded: Successfully provisioned volume pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:30 +0000 UTC - event for inline-volume-tester-9pzx6-my-volume-1: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-ff72x_48654944-1386-4ec0-bff3-21ecb7c169dc } ProvisioningSucceeded: Successfully provisioned volume pvc-d40002aa-1a87-4c32-a28c-258da475be47
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:31 +0000 UTC - event for inline-volume-tester-9pzx6: {default-scheduler } Scheduled: Successfully assigned ephemeral-7577/inline-volume-tester-9pzx6 to ip-172-20-54-148.ap-south-1.compute.internal
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:46 +0000 UTC - event for inline-volume-tester-9pzx6: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-d40002aa-1a87-4c32-a28c-258da475be47" : rpc error: code = Internal desc = Could not attach volume "vol-030e3571bddd79531" to node "i-0eaf0df9fd5dd565c": attachment of disk "vol-030e3571bddd79531" failed, expected device to be attached but was attaching
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:20:46 +0000 UTC - event for inline-volume-tester-9pzx6: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c" : rpc error: code = Internal desc = Could not attach volume "vol-0dff27d9eaec6ce27" to node "i-0eaf0df9fd5dd565c": attachment of disk "vol-0dff27d9eaec6ce27" failed, expected device to be attached but was attaching
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:22:34 +0000 UTC - event for inline-volume-tester-9pzx6: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0 my-volume-1], unattached volumes=[kube-api-access-s4l6t my-volume-0 my-volume-1]: timed out waiting for the condition
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:27:05 +0000 UTC - event for inline-volume-tester-9pzx6: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-1 my-volume-0], unattached volumes=[my-volume-1 kube-api-access-s4l6t my-volume-0]: timed out waiting for the condition
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:29:07 +0000 UTC - event for inline-volume-tester-9pzx6: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-d40002aa-1a87-4c32-a28c-258da475be47" 
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:31:36 +0000 UTC - event for inline-volume-tester-9pzx6: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0], unattached volumes=[kube-api-access-s4l6t my-volume-0 my-volume-1]: timed out waiting for the condition
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:33:53 +0000 UTC - event for inline-volume-tester-9pzx6: {kubelet ip-172-20-54-148.ap-south-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0], unattached volumes=[my-volume-1 kube-api-access-s4l6t my-volume-0]: timed out waiting for the condition
Oct 13 14:36:34.365: INFO: At 2021-10-13 14:35:14 +0000 UTC - event for inline-volume-tester-9pzx6: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-17fbf696-ec5e-46fe-9bed-5f02ff39f47c" 
... skipping 158 lines ...
    [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
    /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should support multiple inline ephemeral volumes [It]
      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:211

      waiting for pod with inline volume
      Unexpected error:
          <*errors.errorString | 0xc00021c0d0>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred

      /tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:307
------------------------------


Summarizing 4 Failures:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (immediate binding)] topology [It] should provision a volume and schedule a pod with AllowedTopologies 
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:180

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Inline-volume (ext4)] volumes [It] should store data 
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath [It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] 
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:713

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral [It] should support multiple inline ephemeral volumes 
/tmp/kops.GBEnirwJi/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:307

Ran 140 of 485 Specs in 1401.370 seconds
FAIL! -- 136 Passed | 4 Failed | 0 Pending | 345 Skipped


Ginkgo ran 1 suite in 24m30.172606826s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 1457 lines ...