ARP entries dropped by DVR routers when the qr device is not ready or present
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Swaminathan Vasudevan |
Bug Description
The ARP entries are dropped by DVR routers when the 'qr' device does not exist in the namespace.
There are two ways in the L3 agent the ARP entries are updated.
Once when an internal csnat port is created, then arp entries added from the 'dvr_local_router' by calling the "set_subnet_
There is another time, when an arp update "rpc" message comes from the Server to the agent as "add_arp_entry" or "delete_arp_entry" which inturn calls "_update_
We have seen log traces that shows that the arp update message comes before the "qr" device is ready. So we get to drop those arp message.
We need to kind of cache those arp messages and update the router-namespace when the "qr" device is ready.
If you see the message below, we are checking for the device and throwing a warning message that the device is not ready, but the arp entries are not saved anywere. They are dropped.
2015-09-24 18:45:30.150 WARNING neutron.
If you see here the internal_network 'qr' device is added later.
2015-09-24 18:45:30.367 DEBUG neutron.
Changed in neutron: | |
status: | New → Confirmed |
assignee: | nobody → Swaminathan Vasudevan (swaminathan-vasudevan) |
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: | added: kilo-backport-potential |
tags: | added: liberty-backport-potential |
tags: | removed: kilo-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | removed: liberty-backport-potential |
In progress. /review. openstack. org/#/c/ 228582/
https:/