Orphaned PVs if provisioner gets killed and restarted

[sbezverk]

Currently there is a check in the provisioner before PV gets deleted for a privisioner ID and if it does not match with the ID of current provisioner PV does not get deleted. While playing for hostpath plugin, I killed and re-created provisioner, as a result provisioner got new ID and refused to delete previous' privisioner created volumes, so bunch of PVs became a sort of orphaned and needed manual deletion.
Maybe we should not check for provisioner identity? What does this check serve for?

[msau42]

+1 I'm seeing this issue. The provisioner ID needs to be persistent across plugin restarts.

[msau42]

Nevermind I saw a different issue: kubernetes/kubernetes#65058

I just tested killing the controller pod in these scenarios and DeleteVolume succeeded:

• After VolumeCreate is successful and before PVC is deleted
• After first VolumeDelete was triggered and before the delete operation completed

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[msau42]

Is this still an issue?

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.