yahoo-eng-team team mailing list archive

[Aaron Rosen <aaronorosen@xxxxxxxxx>]

Public bug reported:

The following migration 50e86cb2637a called
op.rename_table('neutron_nvp_port_mapping', 'neutron_nsx_port_mappings')
though the table name was actually quantum_nvp_port_mapping. Because of this
the quantum_id->nvp_id mapping was never migrated over to the new table and
you would be left with a quantum_nvp_port_mapping table hanging around.

In addition, the downgrade would rename the table to neutron_nvp_port_mapping
instead of quantum_nvp_port_mapping. This patch addresses this issues.

** Affects: neutron
     Importance: High
     Assignee: Aaron Rosen (arosen)
         Status: In Progress


** Tags: havana-backport-potential

** Changed in: neutron
     Assignee: (unassigned) => Aaron Rosen (arosen)

** Changed in: neutron
   Importance: Undecided => High

** Tags added: havana-backport-potential

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

Title:
  Fix Migration 50e86cb2637a

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  The following migration 50e86cb2637a called
  op.rename_table('neutron_nvp_port_mapping', 'neutron_nsx_port_mappings')
  though the table name was actually quantum_nvp_port_mapping. Because of this
  the quantum_id->nvp_id mapping was never migrated over to the new table and
  you would be left with a quantum_nvp_port_mapping table hanging around.

  In addition, the downgrade would rename the table to neutron_nvp_port_mapping
  instead of quantum_nvp_port_mapping. This patch addresses this issues.

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