fix: reduce mount lock to avoid volumeID collision issue

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: reduce mount lock to avoid volumeID collision issue
the volumeHandle(volumeID) could be duplicated in PV, and duplicated volumeHandle(volumeID) is already allowed in latest k8s version, this PR reduces mount lock to avoid volumeID collision issue, the lock only happen when volumeID + stagingPath is the same

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

fix: reduce mount lock to avoid volumeID collision issue

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tzifudzi]

Hi @andyzhangx,

I appreciate your contribution with this fix. That being said, could you please create an issue to reference regarding this error? Alternatively, could you provide some troubleshooting guidance for this fix and how to validate it?

I'm asking because I'm experiencing a problem that I think is related, but I'm not certain. Additional details about the initial issue and the steps leading to this fix would be greatly beneficial. For example, briefly describing how to know if this issue is affecting someone would be helpful.

[andyzhangx]

Hi @andyzhangx,

I appreciate your contribution with this fix. That being said, could you please create an issue to reference regarding this error? Alternatively, could you provide some troubleshooting guidance for this fix and how to validate it?

I'm asking because I'm experiencing a problem that I think is related, but I'm not certain. Additional details about the initial issue and the steps leading to this fix would be greatly beneficial. For example, briefly describing how to know if this issue is affecting someone would be helpful.

@tzifudzi this PR fixed the error An operation with the given Volume ID ... already exists when you have multiple PVs with same volumeHandle value, and it won't fix the smb mount stuck issue which also leads to the above error. if you could make sure your PV has unique volumeHandle value, then this PR won't help.