POD VM fails deleting on AARCH64

Bug #1777742 reported by Patricia Domingues
16
This bug affects 2 people
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.pod.virsh: [error] Failed to get pod CPU speed
Jun 19 15:31:59 d05-3 libvirtd[15047]: 2018-06-19 15:31:59.843+0000: 15047: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error
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-7040-g9bdbbc8-0ubuntu1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS server common files
ii maas-dhcp 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS DHCP server
ii maas-dns 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all dummy transitional package for MAAS DNS server
ii maas-proxy 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS Caching Proxy
ii maas-rack-controller 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all Rack Controller for MAAS
ii maas-region-api 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all Region controller API service for MAAS
ii maas-region-controller 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.5.0~alpha1-7040-g9bdbbc8-0ubuntu1 all MAAS server provisioning libraries (Python 3)

Related branches

Revision history for this message
Newell Jensen (newell-jensen) wrote :

This is actually no architecture specific as my libvirt host, amd64, also supports the --nvram flag for the `undefine` command.

Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
importance: Undecided → Medium
status: New → In Progress
milestone: none → 2.5.x
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.