Detaching multiple NVMe-oF volumes may leave the subsystem in connecting state
Bug #2035375 reported by
Gorka Eguileor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Undecided
|
Gorka Eguileor | ||
Bug Description
When detaching multiple NVMe-oF volumes from the same host we may end with a NVMe subsystem in "connecting" state, and we'll see a bunch nvme error in dmesg.
This happens on storage systems that share the same subsystem for multiple volumes because Nova has not been updated to support the tri-state "shared_targets" option that groups the detach and unmap of volumes to prevent race conditions.
This is related to the issue mentioned in an os-brick commit message: https:/
| Changed in nova: | |
| assignee: | nobody → Gorka Eguileor (gorka) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/