yahoo-eng-team team mailing list archive

[Russell Bryant <1328245@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: nova
    Milestone: None => juno-2

-- 
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/1328245

Title:
  libvirt does not store connection_info after BFV setup

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) havana series:
  Fix Committed
Status in OpenStack Compute (nova) icehouse series:
  In Progress

Bug description:
  If booting from a volume, the virt driver does the setup of the volume
  with cinder before starting the instance. This differs from the attach
  volume case, which is managed by nova itself. Since the connect
  operation could yield new details in the connection_info structure
  that need to be persisted until teardown time, it is important that
  the connection_info be written back after connect completes. Nova's
  attach_volume() does this, but libvirt does not. Specifically in the
  case of the fibre channel code, this means we don't persist
  information about multipath devices which means we don't fully tear
  down everything at disconnect time.

  This is present in at least Havana, and I expect it is present in
  Icehosue and master as well.

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