yahoo-eng-team team mailing list archive

[Yogev Rabl <yrabl@xxxxxxxxxx>]

Public bug reported:

Description of problem:
When running volume attachment on a paused instance, the process seem to succeed, the volume is registered as 'in-use' and there's no error in the nova compute log. 
But when resuming the instance the OS doesn't see the newly attached volume and when trying to detach the volume it fails with the error "DiskNotFound: No disk at vdb" in the nova compute log.

Version-Release number of selected component (if applicable):
python-nova-2013.2.3-6.el6ost.noarch
openstack-nova-compute-2013.2.3-6.el6ost.noarch
python-novaclient-2.15.0-4.el6ost.noarch
openstack-nova-common-2013.2.3-6.el6ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Launch an instance with a working OS with a QCOW image. 
2. Pause the instance.
3. Attach a volume to the instance. 
4. Resume the instance. 
5. In the instance: run the command:
# lsblk

Actual results:
The instance's OS doesn't see the attached volume.

Expected results:
The instance's OS should see the volume.

Additional info:
The nova-compute log is attached. (please notice that the log is very long,

** Affects: nova
     Importance: Undecided
         Status: New

** Attachment added: "volume-attach-fail.log"
   https://bugs.launchpad.net/bugs/1313760/+attachment/4099515/+files/volume-attach-fail.log

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

Title:
  volume attachment fails on a paused instance

Status in OpenStack Compute (Nova):
  New

Bug description:
  Description of problem:
  When running volume attachment on a paused instance, the process seem to succeed, the volume is registered as 'in-use' and there's no error in the nova compute log. 
  But when resuming the instance the OS doesn't see the newly attached volume and when trying to detach the volume it fails with the error "DiskNotFound: No disk at vdb" in the nova compute log.

  Version-Release number of selected component (if applicable):
  python-nova-2013.2.3-6.el6ost.noarch
  openstack-nova-compute-2013.2.3-6.el6ost.noarch
  python-novaclient-2.15.0-4.el6ost.noarch
  openstack-nova-common-2013.2.3-6.el6ost.noarch

  How reproducible:
  100%

  Steps to Reproduce:
  1. Launch an instance with a working OS with a QCOW image. 
  2. Pause the instance.
  3. Attach a volume to the instance. 
  4. Resume the instance. 
  5. In the instance: run the command:
  # lsblk

  Actual results:
  The instance's OS doesn't see the attached volume.

  Expected results:
  The instance's OS should see the volume.

  Additional info:
  The nova-compute log is attached. (please notice that the log is very long,

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