yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #56448
[Bug 1623041] Re: cisco plugin db migration fails due to unknown constraint
It's not neutron issue, it's cisco issue. Changed the project affected.
** Project changed: neutron => networking-cisco
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1623041
Title:
cisco plugin db migration fails due to unknown constraint
Status in networking-cisco:
In Progress
Bug description:
when using cisco networking plugin in liberty and later versions
neutron-db-manage fails for non-innodb engines. This happens due to
relying on autogenerated name for foreign key in cisco_router_mappings
table. In InnoDB it is 'cisco_router_mappings_ibfk_2' - the same name
is used in plugin upgrade() to delete this constraint. Corresponding
file in Cisco plugin is
networking_cisco/db/migration/alembic_migrations/versions/liberty/contract/53f08de0523f_neutron_routers_in_cisco_devices.py
To fix the issue the key must be explicitly named for all other
database backends.
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-cisco/+bug/1623041/+subscriptions
References