[2.4] Bionic no longer needs libvirt-bin to manage virtual machines, instead it can now install libvirt-clients
Bug #1749757 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
I installed MAAS 2.4 in a Bionic container and installed the `libvirt-clients` package in order to manage my libvirt machines.
When I browse to a libvirt-based machine in MAAS and click the "Configuration" tab, I see a spurious error as follows:
Error: Power control software for this power type is missing from the rack controller. To proceed, install the libvirt-bin package on the rack controller.
In Bionic, `libvirt-bin` is no longer required if the machine is just a client to libvirt (and not a hypervisor).
Related branches
~andreserl/maas:better_recommends
- Mike Pontillo (community): Approve
-
Diff: 83 lines (+9/-8)6 files modifieddebian/control (+2/-1)
snap/snapcraft.yaml (+1/-1)
src/provisioningserver/drivers/pod/tests/test_virsh.py (+1/-1)
src/provisioningserver/drivers/pod/virsh.py (+2/-2)
src/provisioningserver/drivers/power/tests/test_virsh.py (+1/-1)
src/provisioningserver/drivers/power/virsh.py (+2/-2)
| Changed in maas: | |
| milestone: | 2.4.x → 2.4.0alpha2 |
| summary: |
- [2.4] Spurious errors on machine configuration page for libvirt machines + [2.4] Bionic no longer needs libvirt-bin, instead it can now install + libvirt-clients |
| summary: |
- [2.4] Bionic no longer needs libvirt-bin, instead it can now install - libvirt-clients + [2.4] Bionic no longer needs libvirt-bin to manage virtual machines, + instead it can now install libvirt-clients |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
