d866ee75c2
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
Team and repository tags
brick
OpenStack Cinder brick library for managing local volume attaches
Features
- Discovery of volumes being attached to a host for many transport protocols.
- Removal of volumes from a host.
Hacking
Hacking on brick requires python-gdbm (for Debian derived distributions), Python 2.7 and Python 3.4. A recent tox is required, as is a recent virtualenv (13.1.0 or newer).
If "tox -e py34" fails with the error "db type could not be determined", remove the .testrepository/ directory and then run "tox -e py34".
- For any other information, refer to the developer documents:
- OR refer to the parent project, Cinder:
- Release notes for the project can be found at:
- License: Apache License, Version 2.0
- Source: https://git.openstack.org/cgit/openstack/os-brick
- Bugs: https://bugs.launchpad.net/os-brick