| 2018-08-24 17:58:55 |
Mike Pontillo |
bug |
|
|
added bug |
| 2018-08-24 17:59:49 |
Mike Pontillo |
maas: milestone |
|
2.5.x |
|
| 2018-08-24 18:00:48 |
Andres Rodriguez |
summary |
[2.5] Errors when starting KVM pod VMs aren't appropriately surfaced |
[2.5, UI] Errors when starting KVM pod VMs aren't appropriately surfaced |
|
| 2018-08-24 18:00:59 |
Andres Rodriguez |
maas: milestone |
2.5.x |
2.5.0beta1 |
|
| 2018-08-24 18:01:03 |
Andres Rodriguez |
maas: importance |
Medium |
High |
|
| 2018-08-24 18:02:34 |
Mike Pontillo |
tags |
ux |
ui ux |
|
| 2018-08-24 18:03:34 |
Mike Pontillo |
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); 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 : virNetDevMacVLanTapOpen:477 : cannot open macvtap tap device /dev/tap11: No such file or directory
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. |
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); 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 : virNetDevMacVLanTapOpen:477 : cannot open macvtap tap device /dev/tap11: No such file or directory
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. |
|
| 2018-08-25 17:21:53 |
Mike Pontillo |
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); 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 : virNetDevMacVLanTapOpen:477 : cannot open macvtap tap device /dev/tap11: No such file or directory
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. |
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 : virNetDevMacVLanTapOpen:477 : cannot open macvtap tap device /dev/tap11: No such file or directory
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. |
|
| 2018-08-28 16:46:29 |
Newell Jensen |
maas: status |
Triaged |
In Progress |
|
| 2018-08-28 16:46:30 |
Newell Jensen |
maas: assignee |
|
Newell Jensen (newell-jensen) |
|
| 2018-08-28 22:22:46 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/353899 |
|
| 2018-08-29 00:34:40 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2018-08-29 01:36:54 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/353902 |
|
| 2018-08-29 01:41:05 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/353903 |
|
| 2018-09-18 07:12:13 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
