Public bug reported:
Changeset I3447ea5bcb7c57365c6f50efe12a1671e86588b3 added a
binding_index column to the RouterL3AgentBinding table, which is unique
with the router_id. However, the current logic isn't concurrent safe as
some concurrent cases can raise a DBDuplicateEntry (if the same
binding_index is being used by 2 different workers).
** Affects: neutron
Importance: Medium
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: l3-dvr-backlog l3-ha
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1633042
Title:
L3 scheduler: make RouterL3AgentBinding always concurrently safe
Status in neutron:
In Progress
Bug description:
Changeset I3447ea5bcb7c57365c6f50efe12a1671e86588b3 added a
binding_index column to the RouterL3AgentBinding table, which is
unique with the router_id. However, the current logic isn't concurrent
safe as some concurrent cases can raise a DBDuplicateEntry (if the
same binding_index is being used by 2 different workers).
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1633042/+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
