Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1510159

Summary: Bug in L3 agent code while cleaning up a router namespace
Product: Red Hat OpenStack Reporter: Brian Haley <bhaley>
Component: openstack-neutronAssignee: Brian Haley <bhaley>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.0 (Liberty)CC: akaris, amuller, bhaley, ccollett, chrisw, ihrachys, jjoyce, nyechiel, pneedle, ragiman, srevivo, tfreger
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 8.0 (Liberty)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-neutron-7.2.0-27.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1508091 Environment:
Last Closed: 2017-11-29 15:59:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1508091, 1510162    
Bug Blocks: 1510157    
Attachments:
Description Flags
l3-agent.log
none
openvswitch-agent.log none

Comment 5 Brian Haley 2017-11-16 20:19:14 UTC 
Toni - just trying to create a lot of routers quickly is the best way to try, but there is no way to trigger the error path manually.
Comment 9 Toni Freger 2017-11-27 13:19:31 UTC 
Created attachment 1359457 [details]
l3-agent.log
Comment 10 Toni Freger 2017-11-27 13:20:09 UTC 
Created attachment 1359458 [details]
openvswitch-agent.log
Comment 11 Brian Haley 2017-11-27 20:18:54 UTC 
Hi Toni,

This trace from arping is something that has been fixed upstream.  Since the arping is happening asynchronously from a greenthread one second a part three times, sometimes the interface or namespace can be cleaned as it's running.  The upstream code now catches this and prints a better message, not throwing the exception.  OSP9 has part of this fix, but the code has been improved more upstream.

The OVS agent log message seem related to the above.  In most cases I can see the agent complaining about a port not being ready, and that port generating an arping error message.

Neither seems related to the change.
Comment 15 errata-xmlrpc 2017-11-29 15:59:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3281