6ea276c22e
nvme-cli no longer allows to use a path to nvme block device (e.g. /dev/nvme0n1) as an argument to nvme disconnect command. For more details, please see: https://github.com/linux-nvme/nvme-cli/issues/563 To address this issue, change the command that is executed to disconnect a volume from: $ nvme disconnect -d <device> to: $ nvme disconnect -n <subnqn> Change-Id: I51a30825da5e7378ebc1d6f4a12645d73d7feb19 Closes-Bug: #1843431 Signed-off-by: Szczerbik, Przemyslaw <przemyslawx.szczerbik@intel.com>
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://opendev.org/openstack/os-brick
- Bugs: https://bugs.launchpad.net/os-brick