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