Reviewed: https://review.openstack.org/357190 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=539d381434ccadcdc3f5d58c2705c35558a3a065 Submitter: Jenkins Branch: master
commit 539d381434ccadcdc3f5d58c2705c35558a3a065 Author: Kevin Zhao <[email protected]> Date: Thu Jan 5 21:32:41 2017 +0000 libvirt: fix nova can't delete the instance with nvram Currently libvirt needs a flag when deleting an VM with a nvram file, without which nova can't delete an instance booted with UEFI. Add deletion flag for NVRAM. Also add a test case. Co-authored-by: Derek Higgins <[email protected]> Change-Id: I46baa952b6c3a1a4c5cf2660931f317cafb5757d Closes-Bug: #1567807 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs Status in OpenStack Compute (nova): Fix Released Status in nova package in Ubuntu: Triaged 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/nova/+bug/1567807/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
