yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57385
[Bug 1629861] Re: L3: missing registry callback notification at Router Interface creation
Changed the title to reflect the case that the bug is in code used also
apparently used by non-DVR setups.
** Summary changed:
- L3 DVR: missing registry callback notification at Router Interface creation
+ L3: missing registry callback notification at Router Interface creation
** Also affects: bgpvpn
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1629861
Title:
L3: missing registry callback notification at Router Interface
creation
Status in networking-bgpvpn:
New
Status in neutron:
In Progress
Bug description:
The code triggering a ROUTER_INTERFACE AFTER_CREATE registry
notification is not ran if the Router to which an interface is added
has no gateway connected.
[1]
https://github.com/openstack/neutron/blob/930655cf57de523181b2d59bb4428b9f23991cce/neutron/db/l3_dvr_db.py#L427
)
This behavior is problematic for components that need to rely on this
functionality, and not consistent with what the non-DVR code does [2].
[2]
https://github.com/openstack/neutron/blob/f4ba9ea8ac18fabac80cb0443bc18d9f950482b3/neutron/db/l3_db.py#L815
To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1629861/+subscriptions
References