-
Notifications
You must be signed in to change notification settings - Fork 81
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 gets stuck intermittently terminating #1375
Comments
never mind I did not see Release 2024-02-07 Bug Fixes Enable HonorPVReclaimPolicy for CSI drivers on AKS 1.27+ to align with upstream behavior. |
Sorry still getting the issues 17m Normal RegisteredNode Node/aks-worker-23918152-vmss000011 Node aks-worker-23918152-vmss000011 event: Registered Node aks-worker-23918152-vmss000011 in Controller |
Just wondering if might be looked at at some point Thank you |
are you using the open source or managed blob csi driver? @EoinMan |
Aks1 K8s == 1.28 csiDriver: v1.29.4 7 mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.29.4 AKs2 K8s == 1.28 csiDriver: v1.29.4 3 mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.29.4 I think its the managed one, |
what do you mean |
So Drivers are installed on the cluster When doing a helm uninstall/delete I get the above error The pod is stuck in a terminating state I can get around or out of the terminating state by deleting the finalizers block of code in the PV If I re-installed the driver on the cluster, I could helm install and helm delete 3/4 times before the issue arose again I could understand the PV hanging if a pod still had a claim |
you could not delete pv if pod or pvc still exists |
I understand that stand The helm uninstall deletes everything The PV is left at the very end stuck in the terminating state This causes issues deploying into that NS again |
What happened:
Upgraded AKS Clusters to 1.28.5
Now getting
Warning VolumeFailedDelete 2m8s persistentvolume-controller error getting deleter volume plugin for volume "PODNAME": no deletable volume plugin matched
Re-install SC
Re-install Drivers
Works for a couple of runs
Then the message re-appears
What you expected to happen:
On Helm uninstall, PV should not get stuck with the error
How to reproduce it:
Anything else we need to know?:
Helm version is v3.14.4
az version 2.60.0
Environment:
uname -a
):The text was updated successfully, but these errors were encountered: