yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #15049
[Bug 1325800] [NEW] Potential Race Condition between L3NATAgent.routers_updated and L3NATAgent._rpc_loop.
Public bug reported:
The _rpc_loop routine takes a snapshot of the L3NATAgent’s
routers_updated set and then it clears the set. At the same time,
L3NATAgent.routers_updated can run, it adds new routers to the
routers_updated set. It is possible for both routines to run at the
same time. So it is possible that _rpc_loop will clear the
routers_updated set right after routers_updated routine added a router
without having the new router included in the snapshot. The problem
will manifests itself by having a newly associated floating ip address
not being configured in the iptables and the qg- device.
** Affects: neutron
Importance: Undecided
Assignee: Stephen Ma (stephen-ma)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Stephen Ma (stephen-ma)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1325800
Title:
Potential Race Condition between L3NATAgent.routers_updated and
L3NATAgent._rpc_loop.
Status in OpenStack Neutron (virtual network service):
New
Bug description:
The _rpc_loop routine takes a snapshot of the L3NATAgent’s
routers_updated set and then it clears the set. At the same time,
L3NATAgent.routers_updated can run, it adds new routers to the
routers_updated set. It is possible for both routines to run at the
same time. So it is possible that _rpc_loop will clear the
routers_updated set right after routers_updated routine added a router
without having the new router included in the snapshot. The problem
will manifests itself by having a newly associated floating ip address
not being configured in the iptables and the qg- device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1325800/+subscriptions
Follow ups
References