yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1598167@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

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

Title:
  rescuing using specified image uses instance's kernel and ramdisk

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When rescue is used with a rescue image specified in the API call the
  kernel and ramdisk used are the ones associated with the instance's
  current image....

  https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L2578

  Note it uses kernel from CONF or instance's kernel, same for ramdisk.

  So assuming CONF.libvirt.rescue_kernel_id or
  CONF.libvirt.rescue_ramdisk_id are not set the behavior will be
  incorrect.

  Thus if rescue image has kernel and ramdisk and instance image does
  not then it will fail to rescue.

  If both instance image and rescue image have kernel and ramdisk then
  the rescue image will use instance image kernel and ramdisk.

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