NVMe-oF: Only connects to first volume
Bug #1964383 reported by
Gorka Eguileor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Fix Released
|
Medium
|
Gorka Eguileor |
Bug Description
For storage systems that share the same subsystem for multiple namespaces and don't support AER namespace messages only the first volume will be able to attach, even when using nvme clients that are not affected by https:/
Error will be os_brick.
This is because the automatic scanning of the Linux nvme driver doesn't get triggered and the os-brick code doesn't issue rescans, at least if drivers are reporting the initial format of the nvme connection properties.
Changed in os-brick: | |
importance: | Undecided → Medium |
Changed in os-brick: | |
status: | New → Triaged |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/c/openstack /os-brick/ +/836060
Review: https:/