yahoo-eng-team team mailing list archive

[Nikola Đipanov <ndipanov@xxxxxxxxxx>]

A patch that does a partial revert of
https://review.openstack.org/49455 from comment #16 and is under
discussion at the time of writing so I am linking it here.

https://review.openstack.org/#/c/175742/

Basically - just checking quotas and not reserving them is a bit of a
fool's errand. We should eithere have a reserve-rollback api in Neutron,
or as has been suggested above - create the port quickly and then update
it with additional information once we have it (when the request reaches
the compute host)

** Changed in: nova
       Status: Fix Released => Confirmed

** Changed in: nova
    Milestone: 2014.2 => None

-- 
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):
  Confirmed

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