Travis Glenn Hansen

I added proper handling of openvpn services in the most recent release. You get a switch for each configuration, you need something more than that?

Agreed. I'll get to it eventually :)

This seemingly non-compliant behavior is quite troubling as an end-user :( especially since it’s known and been floating around for 2.5 years..

In my case, unstage isn't even invoked first...it's just bad order of operations.

Here's my observations so far...scenario, I'm creating 2 pvcs and 2 pods attaching. I then delete the pods, wait for that to finish, then I delete the PVCs. In 1.17.4...

@msau42 yeah, I just deleted the PVCs in the 1.18 cluster after letting it sit for 1.5 hours post pod deletion, and immediately experienced exactly what I described above. 0...

@msau42 I don't see anything. If there was an issue preventing it from calling unstage would that also prevent it from invoking unstage after the PVC is deleted as well?

@saikat-royc in both cases it's using `image: quay.io/k8scsi/csi-provisioner:v1.6.0`, and yes, dynamically provisioned volumes all around.

1. My own implementation here https://github.com/democratic-csi/democratic-csi 2. I'm not sure what the question is here. From the csi side unpublish is invoked (and succeeds)...unstage does not get invoked on 1.18.6...

Wires are getting crossed. I didn’t submit this issue so those are not my logs. My problem is similar but slightly different. In my case unstage is not getting called...