Volume state discrepancy in multi writer mode

[cclerget]

In a testing environment with a shared volume via docker volume by example, a multi-writer volume created/published on "fake" node 1 might not be seen by "fake" node 2, in such case, the volume state is written by node 1 but node 2 doesn't reload the volume state prior to a volume operation as the state is restored/reloaded during driver startup only

[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