Bug 1360352

Summary: [Backport] Race conditions of L3 HA Scheduler
Product: Red Hat OpenStack Reporter: John Schwarz <jschwarz>
Component: openstack-neutronAssignee: John Schwarz <jschwarz>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: amuller, chrisw, dcadzow, ggillies, ihrachys, jlibosva, jschwarz, nyechiel, oblaut, srevivo, swaite, tfreger, tkammer, yfried
Target Milestone: ---Keywords: Automation, AutomationBlocker, FeatureBackport, Triaged, ZStream
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-7.1.1-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1281254 Environment:
Last Closed: 2016-08-24 13:30:29 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: 1281254    
Bug Blocks:    

Comment 2 Toni Freger 2016-08-08 07:26:29 UTC 
Hi John,

We would like to verify this bug, please provide steps to reproduce.

Thanks,
Toni
Comment 3 John Schwarz 2016-08-08 08:06:17 UTC 
There are 2 ways to verify this bug:

1. Simply making sure that the patches are there in the latest version,
2. Running a rally test of "create_and_delete_routers.json" with a high concurrency number (10? 15?), and making sure that the exceptions reported do not happen (i.e. all tests pass and the neutron-server logs do not contain errors).

Obviously the second one is better IMO.

John.
Comment 4 Alexander Stafeyev 2016-08-08 12:43:15 UTC 
code verification 

[root@controller ~]# rpm -qa | grep openstack-neutr
openstack-neutron-openvswitch-7.1.1-4.el7ost.noarch
openstack-neutron-common-7.1.1-4.el7ost.noarch
openstack-neutron-7.1.1-4.el7ost.noarch
openstack-neutron-ml2-7.1.1-4.el7ost.noarch
Comment 6 errata-xmlrpc 2016-08-24 13:30:29 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://rhn.redhat.com/errata/RHBA-2016-1770.html