yahoo-eng-team team mailing list archive

[Balazs Gibizer <1921381@xxxxxxxxxxxxxxxxxx>]

Nova master (Xena) merged the os-brick min version bump in  https://review.opendev.org/c/openstack/nova/+/783674
The stable/wallaby os-brick min version bump is in progress in https://review.opendev.org/c/openstack/nova/+/783822

** Also affects: nova/wallaby
   Importance: Critical
     Assignee: Lee Yarwood (lyarwood)
       Status: Confirmed

** Also affects: nova/xena
   Importance: Undecided
       Status: New

** Changed in: nova/xena
     Assignee: (unassigned) => Lee Yarwood (lyarwood)

** Changed in: nova/xena
       Status: New => Fix Released

** Changed in: nova/xena
   Importance: Undecided => Critical

** Changed in: nova/wallaby
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1921381

Title:
  iSCSI: Flushing issues when multipath config has changed

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) wallaby series:
  In Progress
Status in OpenStack Compute (nova) xena series:
  Fix Released
Status in os-brick:
  In Progress
Status in os-brick wallaby series:
  New
Status in os-brick xena series:
  In Progress

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-connection on Cinder.
  - Not flushing the multipath device (possible data loss) and leaving it as a lefover device similarly to the other case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1921381/+subscriptions