yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

** Changed in: nova
    Milestone: None => grizzly-3

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

Title:
  instance rebuild with volumes attached fails

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  In rebuild, where we call driver.destroy we're not passing a copy of
  the block device mapping, so no attempt is made to disconnect the
  volumes.

  When the new instance is started, it's unable to "check_attach" on the
  already "in-use" volumes.

  2012-10-25 18:43:18 ERROR nova.compute.manager [req-
  d507ef16-dc8a-4259-b509-d85301096872 212975 706689] [instance:
  75083163-7756-49b4-b91c-5bf0bab46de8] Invalid volume: status must be
  available. Setting instance vm_state to ERROR

  passing the block_device_mapping into destroy (as is done in
  terminate) may not be the ideal solution because the mountpoints would
  get lost on the attachments.  Removing the call to check_attach may
  not work since _setup_block_device_mapping is re-used on run_instance
  in _prep_block_device.

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