virsh support requires an extra package to be installed
Bug #1319717 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libvirt (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
| maas (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
In order to manage a virsh node, MAAS needs the libvirt-bin package (which contains `virsh`). libvirt-bin is only a suggested dependency so the virsh power type doesn't work "out of the box."
| tags: | added: power virsh |
Revision history for this message
| Robie Basak (racb) wrote | #1 |
| Changed in maas (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Raphaël Badin (rvb) wrote | #2 |
| Changed in libvirt (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in libvirt (Ubuntu): | |
| status: | New → Triaged |
To post a comment you must log in.
libvirt-bin will pull in libvirtd, which will configure a virbr0, etc. I'm not sure we want to do that by default. I presume this is the original rationale for Suggests rather than Recommends or Depends.
I can see that libvirt might be installed on a different machine though, so perhaps we want virsh available but not libvirtd installed and configured.
Raphaël, does this sound reasonable and is this what you need? If so, I guess we'll need to split libvirt-bin in order to make any progress here.