Description of problem: When creating a tenant and multiple networks neutron gets a love lock due to internal REPEATABLE READ in Kilo Version-Release number of selected component (if applicable): How reproducible: We encountered an issue in Neutron Kilo where adding a tenant with multiple networks in rapid succession results in a stuck Neutron with high CPU utilization.
The fix for the attached launchpad bug was backported and is available in OSP 7 2015.1.2. What version is ALU using?
No response for 3 months, I'm assuming the issue was fixed. I'll tag the bug for eventual inclusion in to errata.
Code verified: openstack-neutron-ml2-2015.1.2-15.el7ost.noarch openstack-neutron-openvswitch-2015.1.2-15.el7ost.noarch
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-2016:1287