NVMeOF connector fails to disconnect a volume with the latest nvme-cli
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Fix Released
|
High
|
Przemyslaw Szczerbik |
Bug Description
Environment:
CentOS Linux release 7.6.1810 (Core)
os-brick (2.9.1)
nvme version 1.9.9.g5221
Description:
os-brick NVMeOF connector fails to disconnect a volume with the latest version of nvme-cli.
As you can see in attached logs, NVMeOF connector attempts to disconnect a volume by executing following command:
$ nvme disconnect -d /dev/nvme0n1
The command fails with 'Failed to disconnect by device name: /dev/nvme0n1' error.
Initially, I suspected this to be nvme-cli issue because I was unable to reproduce it with nvme-cli v1.7.
I reported a bug to nvme-cli maintainer. The maintainer explained that this was intentional change rather than a bug. For more details, please see https:/
This means that os-brick NVMeOF connector has to fixed. It can't use a path to nvme block device (i.e. /dev/nvme0n1). I'd suggest calling nvme disconnect with --nqn parameter, rather than device name.
I would be happy to implement a fix this this issue.