getting double DeleteVolume calls when removing volumes

[jmccormick2001]

I'm seeing double DeleteVolume calls made to our CSI driver. We handle the 2nd call by just dismissing it but this behavior doesn't seem right to me according to the spec.

What happened:

What you expected to happen:

I would expect a single DeleteVolume call made.

How to reproduce it:

Create a volume, delete it.

Anything else we need to know?:

Environment:

• Driver version: "registry.k8s.io/sig-storage/csi-provisioner@sha256:7beede062248204a54ed6813b2d2fb84a99db6d56a824eed483ed1d7965ea6a1" # v5.1.0
• Kubernetes version (use kubectl version): 1.32.0
• OS (e.g. from /etc/os-release): 22.04.3 LTS (Jammy Jellyfish)
• Kernel (e.g. uname -a): 5.15.0-130-generic
• Install tools: k3s
• Others:

[jmccormick2001]

Interesting finding: the problem doesn't seem to occur on this version of Openshift using the latest provisioner (5.2.0), I'm seeing only a single DeleteVolume() call....

Client Version: 4.14.0-202403051609.p0.g286cfa5.assembly.stream.el8-286cfa5 Kustomize Version: v5.0.1 Server Version: 4.16.27 Kubernetes Version: v1.29.10+67d3387

[niranjandarshann]

the issue doesn't appear on this OpenShift version when using the latest provisioner (5.2.0). I only see a single DeleteVolume() call.

[ElijahQuinones]

could potentially be related to https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/issues/176

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.