rescuing using specified image uses instance's kernel and ramdisk
Bug #1598167 reported by
Paul Carlton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
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:/
Note it uses kernel from CONF or instance's kernel, same for ramdisk.
So assuming CONF.libvirt.
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.
Changed in nova: | |
assignee: | nobody → Eli Qiao (taget-9) |
Changed in nova: | |
assignee: | Eli Qiao (taget-9) → nobody |
To post a comment you must log in.
hi Paul
please check if following bug/patch resolve your issue.
https:/ /bugs.launchpad .net/nova/ +bug/1530010
https:/ /review. openstack. org/#/c/ 262388/ 1/nova/ virt/libvirt/ driver. py
Sean put a comment on bug #1530010 , if you have different opinion from it, let me know and I can restore my patch.
Eli.