I confirm the workaround on commment 14 worked also for me. I had this bug after upgrading from Trusty to Xenial using Openstack Mitaka.
You can see the problem in nova-compute.log For Openstack this is very nasty bug because everything will fail to be scheduled on that compute-node, but the neutron port will not be cleaned up. So when finally the instance will be spawned on another compute node, it will come up with two neutron ports and two IP addresses. ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1583009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs