Reviewed: https://review.openstack.org/283802 Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=057fb2f3bd5970ff865dcc0fd8822498f40504dc Submitter: Jenkins Branch: master
commit 057fb2f3bd5970ff865dcc0fd8822498f40504dc Author: Stephen Balukoff <step...@balukoff.com> Date: Tue Feb 23 12:55:50 2016 -0800 Fix shared-pools lbaas_listeners migration This patch fixes the MySQL-specific features in the alembic migration for shared-pools, so that migrations can also work on PostgreSQL. This patch also removes the uniqueness of the SQLAlchemy model definition of the Listener.default_pool_id field. (This was mistakenly left in place in the shared-pools patch.) Closes-Bug: 1549372 Closes-Bug: 1548807 Change-Id: Ib1896997f2e7a505b5bf8ec0c9e5ee35942f79a6 ** Changed in: neutron Status: In Progress => 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/1549372 Title: shared-pools patch leaves unique index on Listener.default_pool_id Status in neutron: Fix Released Bug description: In the shared-pools patch, I mistakenly forgot to update the SQLAlchemy model definition of the listener to remove the 'uniqueness' of the Listener.default_pool_id property. While this restriction is in place, it's not possible for two listeners to share the same default_pool (which is one of the purposes of the patch, along with preparation for deploying the L7 code). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1549372/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp