Public bug reported: The migration contained in neutron_lbaas/db/migration/alembic_migrations/versions/mitaka/expand/6aee0434f911_independent_pools.py drops the foreign key constraints from the lbaas_listeners table. It contains code for both PostgreSQL and MySQL, however, the MySQL path is only compatible with the innodb engine. The ndbcluster engine assigns random names to foreign keys unless told otherwise, resulting in the code erroring out when it tries to reference "lbaas_listeners_ibfk_2". This can be fixed using sqlalchemy's reflection feature to look up the foreign key names before dropping.
** Affects: neutron Importance: Undecided Assignee: Paul Bourke (pauldbourke) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1643829 Title: [neutron-lbaas] Migration contains innodb specific code Status in neutron: In Progress Bug description: The migration contained in neutron_lbaas/db/migration/alembic_migrations/versions/mitaka/expand/6aee0434f911_independent_pools.py drops the foreign key constraints from the lbaas_listeners table. It contains code for both PostgreSQL and MySQL, however, the MySQL path is only compatible with the innodb engine. The ndbcluster engine assigns random names to foreign keys unless told otherwise, resulting in the code erroring out when it tries to reference "lbaas_listeners_ibfk_2". This can be fixed using sqlalchemy's reflection feature to look up the foreign key names before dropping. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1643829/+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