Public bug reported:
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. To fix the issue the
key must be explicitly named for all other database backends.
** Affects: neutron
Importance: Undecided
Assignee: Vladislav Belogrudov (vlad-belogrudov)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Vladislav Belogrudov (vlad-belogrudov)
--
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 neutron:
New
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. 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/neutron/+bug/1623041/+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
