[2.5, UI] Errors when starting KVM pod VMs aren't appropriately surfaced
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Newell Jensen |
Bug Description
I am testing with a privileged LXD container running MAAS and libvirt as a KVM pod.
In this configuration, I am not able to use a macvlan (macvtap) attachment (due to being in a container - see also bug #1788952); when I use an `interfaces` constraint that forces a macvlan attachment (manually requesting an interface on the pod host known to not be a bridge) it fails with an error such as the following when starting the VM (found in the syslog, or when starting the composed VM manually via virsh):
342: error : virNetDevMacVLa
When the VM is allocated with skip_commissioning, MAAS never tries to start it; it remains in "Ready" state and the user would never know there is an issue until they go to deploy (it fails with "Failed Deployment").
If the VM is manually composed without skip_commissioning, MAAS attempts commissioning, and commissioning immediately fails with "Failed Commissioning", with no indication about what the error was or why it occurred.
Related branches
- MAAS Lander: Approve
- Mike Pontillo (community): Approve
-
Diff: 148 lines (+64/-0)2 files modifiedsrc/provisioningserver/drivers/pod/tests/test_virsh.py (+43/-0)
src/provisioningserver/drivers/pod/virsh.py (+21/-0)
Changed in maas: | |
milestone: | none → 2.5.x |
tags: | added: ui |
description: | updated |
description: | updated |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I'm making this a UI issue as well.