octavia

[neutron-lbaas] Migration contains innodb specific code

Bug #1643829 reported by Paul Bourke on 2016-11-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
​ octavia
In Progress
Medium
Paul Bourke
Also affects project (?) Also affects distribution/package Nominate for series

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.

OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lbaas (master)

Fix proposed to branch: master
Review: https://review.openstack.org/400666

Changed in neutron:
assignee: nobody → Paul Bourke (pauldbourke)
status: New → In Progress
Kevin Benton (kevinbenton) on 2016-11-22
Changed in neutron:
importance: Undecided → Medium
tags: added: db lbaas
Michael Johnson (johnsom) on 2016-12-01
affects: neutron → octavia
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron-lbaas (master)

Change abandoned by Paul Bourke (pbourke) (<email address hidden>) on branch: master
Review: https://review.openstack.org/400666

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.
Subscribing...

Other bug subscribers