Saw this report just now, but we had the same issue and were caused by slow quantum server. In addition to port created by scheduler retrying request on a different compute, we also have a bug in the quantum client as reported here https://bugs.launchpad.net/neutron/+bug/1267649. We were able to fix this temporarily by increasing the timeout value for the quantum_url_timeout property in nova compute to larger values, 2 minutes in our case.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160442 Title: when boot many vms with quantum, nova sometimes allocates two quantum ports rather than one To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1160442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs