yahoo-eng-team team mailing list archive

[Andrew Melton <andrew.melton@xxxxxxxxxxxxx>]

Public bug reported:

When boot from block/volume was started for libvirt-lxc, a check was
added to _create_domain_setup_lxc that uses disk_info to determine
whether or not the instance was booted from block. While the spawn call
provides disk_info via a kwarg to _create_domain_and_network, many other
operations leave that information off. These calls now need to provide
disk_info to _create_domain_and_network so that it is available to
determine whether or not the instance was booted from block/volume.
Without that data, the check will erroneously determine that the
instance was booted from a volume.

Steps to reproduce:
1) Create devstack with local.conf: https://gist.github.com/ramielrowe/520b0b86a5adf385b45d
2) Boot instance from image
3) Stop the instance
4) Start the instance
5) Observe exception in nova-compute logs: https://gist.github.com/ramielrowe/5cc2cb372fd019ee8331

In the stack trace you can see Nova has attempted to set up the instance
as if it was booted from volume.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Libvirt _create_domain_and_network calls missing disk_info

Status in OpenStack Compute (Nova):
  New

Bug description:
  When boot from block/volume was started for libvirt-lxc, a check was
  added to _create_domain_setup_lxc that uses disk_info to determine
  whether or not the instance was booted from block. While the spawn
  call provides disk_info via a kwarg to _create_domain_and_network,
  many other operations leave that information off. These calls now need
  to provide disk_info to _create_domain_and_network so that it is
  available to determine whether or not the instance was booted from
  block/volume. Without that data, the check will erroneously determine
  that the instance was booted from a volume.

  Steps to reproduce:
  1) Create devstack with local.conf: https://gist.github.com/ramielrowe/520b0b86a5adf385b45d
  2) Boot instance from image
  3) Stop the instance
  4) Start the instance
  5) Observe exception in nova-compute logs: https://gist.github.com/ramielrowe/5cc2cb372fd019ee8331

  In the stack trace you can see Nova has attempted to set up the
  instance as if it was booted from volume.

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