yahoo-eng-team team mailing list archive

[Lee Yarwood <1921381@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/wallaby
       Status: Fix Committed => Fix Released

-- 
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):
  Fix Committed
Status in OpenStack Compute (nova) wallaby series:
  Fix Released
Status in OpenStack Compute (nova) xena series:
  Fix Released
Status in os-brick:
  Fix Committed
Status in os-brick queens series:
  Triaged
Status in os-brick rocky series:
  Triaged
Status in os-brick stein series:
  Triaged
Status in os-brick train series:
  Fix Committed
Status in os-brick ussuri series:
  In Progress
Status in os-brick victoria series:
  Fix Committed
Status in os-brick wallaby series:
  Fix Released
Status in os-brick xena series:
  Fix Committed

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