This bug was fixed in the package nova - 2:13.1.3-0ubuntu1~cloud0 ---------------
nova (2:13.1.3-0ubuntu1~cloud0) trusty-mitaka; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . nova (2:13.1.3-0ubuntu1) xenial; urgency=medium . * New upstream point release for OpenStack Mitaka. (LP: #1668313) * d/patches/uefi-delete-instances.patch: Fix deletion of instances with UEFI is enabled. (LP: #1567807) ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in Ubuntu Cloud Archive newton series: Fix Committed Status in Ubuntu Cloud Archive ocata series: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Xenial: Fix Released Status in nova source package in Yakkety: Fix Committed Status in nova source package in Zesty: Fix Released Bug description: I've been setting up a Mitaka Openstack using the cloud archive running on Trusty, and am having problems working with EFI enabled instances on ARM64. I've done some work with wgrant and gotten things to a stage where I can boot instances, using the aavmf images. However, when I tried to delete a VM booted like this, I get an error: libvirtError: Requested operation is not valid: cannot delete inactive domain with nvram I've included the full traceback at https://paste.ubuntu.com/15682718/. Thanks to a suggestion from wgrant again, I got it working by editing nova/virt/libvirt/guest.py in delete_configuration() and replacing self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE) with self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE | libvirt.VIR_DOMAIN_UNDEFINE_NVRAM). I've attached a rough patch. Once that's applied and nova-compute restarted, I was able to delete the instance fine. Could someone please investigate this and see if its the correct fix, and look at getting it fixed in the archive? This was done on a updated trusty deployment using the cloud-archives for mitaka. $ dpkg-query -W python-nova python-nova 2:13.0.0~b2-0ubuntu1~cloud0 Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1567807/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp