This appears to be fixed upstream as of Newton via bug https://bugs.launchpad.net/nova/+bug/1646255 for which the following patch was provided:
commit f0d44c5b09f3f3c84038d40b621bb629a1f8110e Author: Matt Riedemann <mrie...@us.ibm.com> Date: Sun Dec 4 15:08:04 2016 -0500 Handle ComputeHostNotFound when listing hypervisors Compute node resources must currently be deleted manually in the database, and as such they can reference service records which have been deleted via the services delete API. Because of this when listing hypervisors (compute nodes), we may get a ComputeHostNotFound error when trying to lookup a service record for a compute node where the service was deleted. This causes the API to fail with a 500 since it's not handled. This change handles the ComputeHostNotFound when looping over compute nodes in the hypervisors index and detail methods and simply ignores them. Change-Id: I2717274bb1bd370870acbf58c03dc59cee30cc5e Closes-Bug: #1646255 ** Changed in: nova (Ubuntu) Status: New => Triaged ** Changed in: nova (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739253 Title: Removing nova-compute unit with scheduled but stopped VM breaks hypervisor-list api call To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1739253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs