When user runs two pods that use the same PV we send this event: Multi-Attach error for volume "pvc-61e094bc-b375-11e7-b95b-02d8407159d1" Volume is already exclusively attached to one node and can't be attached to another. What we should do: - check on what node is the volume attached - check if there is a pod on the node that uses the volume - if so, send an event to user that explicitly mentions that pod XYZ already uses the volume and it must be killed first - if not, log an error that would say where the volume is attached and that there is no pod that uses it and something is badly broken. We should send an event somewhere, but not to user - he can't do anything with it.
> - if not, log an error that would say where the volume is attached and > that there is no pod that uses it and something is badly broken. We should > send an event somewhere, but not to user - he can't do anything with it. Still, the user should see something so he knows what's going on and he can ask admin to fix it (or fill a bug and we'll see at least the faulty nodes). Upstream PR: https://github.com/kubernetes/kubernetes/pull/56288 (sends both events to user)
still pending upstream...
Origin 3.9 PR: https://github.com/openshift/origin/pull/18290
Merged today
Verified on v3.9.0-0.47.0 Steps 1. Create a PV with block volume, gluster-block for example 2. Create an RC with replicas=2 3. Verify the description for multi-attach: ``` Warning FailedAttachVolume 1h attachdetach-controller Multi-Attach error for volume "pvc-bb2d1def-177d-11e8-b77c-0050569f5abb" Volume is already used by pod(s) vpod-skhtb ```
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489