Public bug reported: Connecting an external network to a router causes l3-agent to send out gratuitous arp packets to to the external network gateway IP in order to pre-populate the mac table without expecting a response. Similar behavior when associating floating IPs. Arping utility on CentOS7.2 returns 0 when no response but returns 1 on Ubuntu14.04 which causes an exception and thus a Traceback in the log files.
Changing arping command call to not check return code status fixes this issue and that is the proposed fix. Pre-conditions: Router with external network attached. Step-by-step reproduction steps: 1) Create a router 2) Attach an external network as gateway. 3) Attach a tenant network to the router. 4) Associate a Floating IP to a VM instance powered on in that tenant network. Expected output: No errors in logs. Seen on CentOS7.2 Actual output: Traceback in l3 log. Seen on Ubuntu14.04 http://paste.openstack.org/show/496284/ Version: Openstack Liberty (Tag: 7.0.2). Ubuntu14.04. uname -a Linux ubuntu01 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Services running: l3-agent in dvr mode, ovs-agent, dhcp-agent, nova- compute. Perceived Severity: Medium (Causes issues with active monitoring) ** Affects: neutron Importance: Undecided Assignee: Arun (sarun87) Status: New ** Changed in: neutron Assignee: (unassigned) => Arun (sarun87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1578842 Title: gratuitous arping causes exception filling up logs with errors on Ubuntu14.04 Status in neutron: New Bug description: Connecting an external network to a router causes l3-agent to send out gratuitous arp packets to to the external network gateway IP in order to pre-populate the mac table without expecting a response. Similar behavior when associating floating IPs. Arping utility on CentOS7.2 returns 0 when no response but returns 1 on Ubuntu14.04 which causes an exception and thus a Traceback in the log files. Changing arping command call to not check return code status fixes this issue and that is the proposed fix. Pre-conditions: Router with external network attached. Step-by-step reproduction steps: 1) Create a router 2) Attach an external network as gateway. 3) Attach a tenant network to the router. 4) Associate a Floating IP to a VM instance powered on in that tenant network. Expected output: No errors in logs. Seen on CentOS7.2 Actual output: Traceback in l3 log. Seen on Ubuntu14.04 http://paste.openstack.org/show/496284/ Version: Openstack Liberty (Tag: 7.0.2). Ubuntu14.04. uname -a Linux ubuntu01 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Services running: l3-agent in dvr mode, ovs-agent, dhcp-agent, nova- compute. Perceived Severity: Medium (Causes issues with active monitoring) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1578842/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
