yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1243213] Re: Enums are not deleted after dropping tables in some migrations

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Thu, 04 Sep 2014 14:09:44 -0000
Reply-to: Bug 1243213 <1243213@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

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

Title:
  Enums are not deleted after dropping tables in some migrations

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

Bug description:
  For downgrade with postgres it is not enough to just drop_table if table contains enums. They should be removed separately after
  deleting the table.

  This problem takes place in migrations like
  52ff27f7567a_support_for_vpnaas, 39cf3f799352_fwaas_havana_2_model,
  569e98a8132b_metering, f489cf14a79c_lbaas_havana.

  Also if some migration use the same enums in postgres work with
  them should be organized differently. In migration 3c6e57a23db4_add_multiprovider if does not use create_type=False downgrade fails  with this error http://paste.openstack.org/show/84486/

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