yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: quantum
       Status: Fix Committed => Fix Released

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

Title:
  nvp_port_mapping breaks upgrade from folsom for NVP users

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  The Grizzly version of the NVP plugin stores the NVP port identifier
  alongside the Quantum port id, in order to be able to perform a
  simpler query on NVP when fetching the port.

  However, these mapping are not populated when upgrading the database from folsom to grizzly, and this leads to errors because:
  - the mapping is not found and a PortNotFound is raised, or
  - the mapping is not found and a 'None' port_id is sent to NVP, causing the query to fail and a 500 to be returned to the quantum user.

  In order to fix this bug retrieval of ports from Quantum should
  contemplate the case in which the port mapping is not found in the
  quantum database, and query NVP in that case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1153616/+subscriptions