Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pv is getting stuck in terminating state after upgrading the external provisioner to v5.1.0 latest release #1277

Open
ramandeepsharma opened this issue Sep 23, 2024 · 4 comments

Comments

@ramandeepsharma
Copy link

ramandeepsharma commented Sep 23, 2024

What happened:

pv is getting stuck in terminating state after upgrading the external provisioner to v5.1.0 latest release. The issue seems to be caused by patch permissions which got added here: PR-1155. We have to delete the finalizer as well as pv manually currently.

What you expected to happen:

pv shouldn't get stuck in terminating and should get deleted without removing the finalizer.

How to reproduce it:

Anything else we need to know?:

We also noticed the following driver logs during pv termination and looks like because of these errors, provisioner is not being able to delete the PV.

Warning VolumeFailedDelete 44s (x379 over 23h) efs.csi.aws.com_efs-csi-controller-6d9d89f7c7-xxxx rpc error: code = NotFound desc = Failed to find access point for volume: fs-xxxxxx

Environment:

  • Driver version: v2.0.7 (helm chart version: 3.0.8)
  • Kubernetes version (use kubectl version): v1.29
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@Jainbrt
Copy link

Jainbrt commented Sep 28, 2024

@ramandeepsharma what is exact minor version of K8s, you are running ?

@ramandeepsharma
Copy link
Author

@Jainbrt Exact K8s version is 1.29.8

@Jainbrt
Copy link

Jainbrt commented Oct 7, 2024

it should work with 1.29.8, while I am hoping that you are using the latest provisioner too (5.1.0)

@ramandeepsharma
Copy link
Author

ramandeepsharma commented Nov 26, 2024

Yes I tried it with 1.29.8 and already using 5.1.0 provisioner. however issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants