yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51044
[Bug 1172808] Re: Nova fails on Quantum port quota too late
This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. This bug can be reopened (set back
to "New") if someone decides to work on this.
FWIW, I guess this is also part of the bp "get-me-a-network":
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/get-
me-a-network.html
** Changed in: nova
Status: Confirmed => Opinion
--
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/1172808
Title:
Nova fails on Quantum port quota too late
Status in OpenStack Compute (nova):
Opinion
Bug description:
Currently Nova will only hit any port quota limit in Quantum in the
compute manager - as that's where the code to create ports exists -
resulting in the instance going to an error state (after its bounced
through three hosts).
Seems to me that for Quantum the ports should be created in the API
call (so that the error can be sent back to the user), and the port
then passed down to the compute manager.
(Since a user can pass a port into the server create call I'm assuming
this would be OK)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1172808/+subscriptions