Parallel HyperDisk Clones fail with: rpc error: code = Aborted desc = An operation with the given Volume ID <> already exists

[karkunpavan]

This issue was reported by our partner Redhat openshift during their testing.

Reproduction steps:

1. Create multiple DVs cloning (via VolumeSnapshot) the same PVC (example). Try to increase the number of clone DVs created "concurrently" until you reproduce the issue.
2. Some of the DVs will get stuck in PrepClaimInProgress phase and their VolumeSnapshots will report the following error:
   Failed to check and update snapshot content: failed to take snapshot of the volume projects//zones/us-central1-c/disks/pvc-: "rpc error: code = Aborted desc = An operation with the given Volume ID projects//zones/us-central1-c/disks/pvc- already exists"

The error seems to be coming from the volume-lock logic here.

[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