yahoo-eng-team team mailing list archive

["Davanum Srinivas \(DIMS\)" <davanum@xxxxxxxxx>]

This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to
''New''.

** Changed in: nova (Ubuntu)
       Status: Triaged => Invalid

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

Title:
  Attaching volume during instance boot doesn't work

Status in OpenStack Compute (Nova):
  Incomplete
Status in “nova” package in Ubuntu:
  Invalid

Bug description:
  Using the newly enabled volume support on canonistack, it arrived at a
  state where the volume believed it was in-use by the instance, but the
  instance had not registered it. The volume then refused to be detached
  from the instance, the command succeeded but no change occurred.

  The sequence of events was:
  * Start instance (using ubuntu-precise-12.04-i386-server-20120424 image)
  * Create volume
  * Wait till instance was listed as ACTIVE (volume was also available at this point)
  * Attach volume
  * SSH to instance... fails, instance not yet booted enough
  * Wait more (took quite a long time)
  * SSH to instance
  * dmesg contains nothing about volume

  The suggestion is the attach happened to soon in the boot process.

  To recover, did:
  * Reboot instance
  * Wait till instance is listed as ACTIVE and can SSH to it
  * Volume is now back to being available
  * Attach volume
  * dmesg contains information about the new volume

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