libvirt inject_data assumes instance with kernel_id doesn't contain a partition table
Bug #1290455 reported by
Matthew Booth
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Unassigned |
Bug Description
libvirt/driver.py passes partition=None to disk.inject_data() for any instance with kernel_id set. partition=None means that inject_data will attempt to mount the whole image, i.e. assuming there is no partition table. While this may be true for EC2, it is not safe to assume that Xen images don't contain partition tables. This should check something more directly related to the disk image. In fact, ideally it would leave it up to libguestfs to work it out, as libguestfs is very good at this.
tags: | added: libvirt |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
importance: | Undecided → Wishlist |
Changed in nova: | |
assignee: | nobody → Saranya Pandian (saranya-pandian) |
Changed in nova: | |
assignee: | Saranya Pandian (saranya-pandian) → nobody |
To post a comment you must log in.
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.
In case you want to work on that, consider writing a blueprints [1] and spec [2]. I'll recommend to read [3] if not yet done. The effort to implement the requested feature is then driven only by the blueprint (and spec).
References: /blueprints. launchpad. net/nova/ /github. com/openstack/ nova-specs /wiki.openstack .org/wiki/ Blueprints
[1] https:/
[2] https:/
[3] https:/