os-brick/os_brick
Gorka Eguileor d866ee75c2 Fix multipath disconnect with path failure
Under certain conditions detaching a multipath device may result on
failure when flushing one of the individual paths, but the disconnect
should have succeeded, because there were other paths available to flush
all the data.

OS-Brick is currently following standard recommended disconnect
mechanism for multipath devices:

- Release all device holders
- Flush multipath
- Flush single paths
- Delete single devices

The problem is that this procedure does an innecessary step, flushing
individual single paths, that may result in an error.

Originally it was thought that the individual flushes were necessary to
prevent data loss, but upon further study of the multipath-tools and the
device-mapper code it was discovered that this is not really the case.

After the multipath flushing has been completed we can be sure that the
data has been successfully sent and acknowledge by the device.

Closes-Bug: #1785669
Change-Id: I10f7fea2d69d5d9011f0d5486863a8d9d8a9696e
2018-08-13 11:02:01 +02:00
..
encryptors Make close on cryptsetup volumes idempotent 2017-11-18 00:19:42 +00:00
initiator Fix multipath disconnect with path failure 2018-08-13 11:02:01 +02:00
local_dev Remove the unnecessary pv_list assign during LVM object init 2018-01-11 00:59:31 +00:00
privileged Refactor iSCSI connect 2017-06-16 16:09:35 +02:00
remotefs Merge "Windows SMBFS: avoid mounting local shares by default" 2018-07-16 18:45:11 +00:00
tests Fix multipath disconnect with path failure 2018-08-13 11:02:01 +02:00
__init__.py doc: Remove cruft from conf.py 2017-08-08 15:44:29 +01:00
exception.py Refactor iSCSI connect 2017-06-16 16:09:35 +02:00
executor.py iSCSI multipath: improve logging on connect 2017-06-26 20:31:59 +02:00
i18n.py Update and replace http with https for doc links 2017-07-26 02:18:44 +00:00
utils.py Mask passwords in utils.trace for func params 2016-11-08 12:55:46 -05:00
version.py Add reno for release notes management 2016-01-20 19:19:36 -06:00