yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1166770] Re: nova boot with colume should fail if the volume is already attached to another instance

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Alan Pevec <1166770@xxxxxxxxxxxxxxxxxx>
Date: Thu, 08 Aug 2013 19:54:19 -0000
Reply-to: Bug 1166770 <1166770@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova/grizzly
       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/1166770

Title:
  nova boot with colume should fail if the volume is already attached to
  another instance

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Released

Bug description:
  When creating a new instance using "nova boot --block-device-mapping"
  and requesting a volume to be attached as either the boot medium or
  additional storage, the volume is attached to the new instance
  regardless of its current state.

  Expected behaviour is to refuse to attach a volume to a new instance
  if that volume is attached elsewhere in exactly the same way that
  attaching existing volumes to existing instances works.

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