yahoo-eng-team team mailing list archive

[Mark McClain <1172808@xxxxxxxxxxxxxxxxxx>]

We'll continue to track this bug in Quantum to discuss the changes, but
ultimately we'll have to update Nova.

** Changed in: quantum
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1172808

Title:
  Nove fails on Quantum port quota too late

Status in OpenStack Compute (Nova):
  New
Status in OpenStack Quantum (virtual network service):
  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