iSCSI: Flushing issues when multipath config has changed
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
OpenStack Compute (nova) | ||||||
Wallaby |
Fix Released
|
Critical
|
Lee Yarwood | |||
Xena |
Fix Released
|
Critical
|
Lee Yarwood | |||
os-brick |
Fix Committed
|
Critical
|
Gorka Eguileor | |||
Queens |
Triaged
|
Undecided
|
Unassigned | |||
Rocky |
Triaged
|
Undecided
|
Unassigned | |||
Stein |
In Progress
|
Undecided
|
Sofia Enriquez | |||
Train |
Fix Released
|
Critical
|
Luigi Toscano | |||
Ussuri |
Fix Released
|
Critical
|
Luigi Toscano | |||
Victoria |
Fix Released
|
Critical
|
Sofia Enriquez | |||
Wallaby |
Fix Released
|
Critical
|
Unassigned | |||
Xena |
Fix Released
|
Critical
|
Gorka Eguileor |
Bug Description
OS-Brick disconnect_volume code assumes that the use_multipath parameter that is used to instantiate the connector has the same value than the connector that was used on the original connect_volume call.
Unfortunately this is not necessarily true, because Nova can attach a volume, then its multipath configuration can be enabled or disabled, and then a detach can be issued.
This leads to a series of serious issues such as:
- Not flushing the single path on disconnect_volume (possible data loss) and leaving it as a leftover device on the host when Nova calls terminate-
- Not flushing the multipath device (possible data loss) and leaving it as a lefover device similarly to the other case.
summary: |
- Flushing issues when multipath config has changed + iSCSI: Flushing issues when multipath config has changed |
Changed in os-brick: | |
milestone: | none → 4.3.1 |
status: | New → In Progress |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Lee Yarwood (lyarwood) |
tags: | added: wallaby-rc-potential |
no longer affects: | nova |
tags: | added: iscsi multipath |
Fix proposed to branch: master /review. opendev. org/c/openstack /os-brick/ +/782992
Review: https:/