yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. If you decide to work on this
consider using a blueprint [1] (maybe with a spec [2]). I'll recommend to 
read [3] if not yet done. 

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints

** Changed in: nova
       Status: Confirmed => Opinion

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

Title:
  Volume cannot be attached via VirtIO while batting from ISO

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  I am using a Nova version 2014.2.2 setup with VirtIO. I am trying to
  attach a volume via VirtIO driver to a machine with an ISO boot image.
  However, nova does not create a configuration for the volume attaching
  it via VirtIO but rather via IDE. The following steps are causing the
  problem.

  First I create a new instance, which works fine:

  nova boot --flavor 1 --image gentoo.iso --nic net-
  id=bea32667-0d4d-4546-877a-9cff5551d164 test-vm

  Then I try to attach a volume via VirtIO. I will explain, why I use
  vdb later:

  nova volume-attach test-vm 28c2ce69-4430-4216-8758-3fe4a3d8d322
  /dev/vdb

  The volume is then attached as /dev/hdb to the instance instead of
  /dev/vdb. The log shows the following:

  2015-02-25 16:44:04.028 10549 DEBUG nova.compute.utils [req-934ddef9
  -103a-4ad0-b05c-12f0857b9174 None] Using /dev/hd instead of /dev/vd
  get_next_device_name /usr/lib64/python2.7/site-
  packages/nova/compute/utils.py:174

  When I try to attach the volume to /dev/vda it fails completely,
  because then Nova tries to attach it to /dev/hda that it assumes to be
  already occupied by the cdrom emulation with the ISO image.

  I looked into the utils.py file and could not really figure out the
  reason why the prefix is created based on the root device name. So I
  am not sure whether this is a bug or intended functionality. In the
  latter case I would appreciate an explanation especially how to
  enforce the attachment via VirtIO only for the one device in question.

  Thank you and best regards

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