POD VM fails deleting on AARCH64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Newell Jensen |
Bug Description
MAAS doesn't delete pod VM from the host on AARCH64.
Log shows as deleted and interface doens't show it, but
it is still in the host.
steps:
a. create a virsh pod
b. compose and deploy a machine
c. delete machine via MAAS interface
infos:
maas.log
Jun 19 15:31:57 d05-3 maas.node: [info] unique-cod: Decomposing machine
Jun 19 15:31:58 d05-3 systemd[1]: Started Session 11922 of user ubuntu.
Jun 19 15:31:59 d05-3 maas.drivers.
Jun 19 15:31:59 d05-3 libvirtd[15047]: 2018-06-19 15:31:59.843+0000: 15047: error : virNetSocketRea
Jun 19 15:31:59 d05-3 maas.node: [info] unique-cod: Deleting machine
...
Jun 19 15:32:13 d05-3 sh[54914]: #011 * removed node unique-cod
but VM is still in the host:
~$ sudo virsh list --all
Id Name State
-------
- unique-cod shut off
when try to delete it:
$ sudo virsh undefine unique-cod
error: Failed to undefine domain unique-cod
error: Requested operation is not valid: cannot undefine domain with nvram
but it works adding '--nvram': "sudo virsh undefine unique-cod --nvram"
Output from "dpkg -l '*maas*'|cat":
||/ Name Version Architecture Description
+++-===
ii maas 2.5.0~alpha1-
ii maas-cli 2.5.0~alpha1-
un maas-cluster-
ii maas-common 2.5.0~alpha1-
ii maas-dhcp 2.5.0~alpha1-
ii maas-dns 2.5.0~alpha1-
ii maas-proxy 2.5.0~alpha1-
ii maas-rack-
ii maas-region-api 2.5.0~alpha1-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.5.0~alpha1-
ii python3-maas-client 2.5.0~alpha1-
ii python3-
Related branches
- Andres Rodriguez (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 30 lines (+4/-4)2 files modifiedsrc/provisioningserver/drivers/pod/tests/test_virsh.py (+2/-3)
src/provisioningserver/drivers/pod/virsh.py (+2/-1)
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.5.x → 2.5.0alpha1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
This is actually no architecture specific as my libvirt host, amd64, also supports the --nvram flag for the `undefine` command.