virsh probe-and-enlist does not set boot order
Bug #1457921 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
Bug Description
To be consistent with SeaMicro and VMware, the virsh probe-and-enlist should set the boot order of each enlisted VM to be (network, hd) in order to ensure MAAS works correctly after the first PXE install.
Related branches
lp:~mpontillo/maas/virsh-configure-pxe-during-probe-and-enlist
- Blake Rouse (community): Approve
-
Diff: 393 lines (+174/-24)3 files modifiedsrc/provisioningserver/drivers/hardware/tests/test_virsh.py (+83/-6)
src/provisioningserver/drivers/hardware/virsh.py (+90/-18)
src/provisioningserver/import_images/tests/test_boot_resources.py (+1/-0)
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | none → 1.8.0 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
