Bug 1315338

Summary:	fix _ensure_default_security_group logic
Product:	Red Hat OpenStack	Reporter:	Pablo Iranzo Gómez <pablo.iranzo>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	amuller, chrisw, nyechiel, pablo.iranzo, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2015.1.2-14.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-22 19:16:58 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:
Bug Blocks:	1214764

Description Pablo Iranzo Gómez 2016-03-07 13:49:54 UTC

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.

Comment 3 Assaf Muller 2016-03-07 23:31:15 UTC

The fix for the attached launchpad bug was backported and is available in OSP 7 2015.1.2. What version is ALU using?

Comment 5 Assaf Muller 2016-06-04 18:07:44 UTC

No response for 3 months, I'm assuming the issue was fixed. I'll tag the bug for eventual inclusion in to errata.

Comment 9 Toni Freger 2016-06-22 13:46:18 UTC

Code verified:
openstack-neutron-ml2-2015.1.2-15.el7ost.noarch
openstack-neutron-openvswitch-2015.1.2-15.el7ost.noarch

Comment 11 errata-xmlrpc 2016-06-22 19:16:58 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-2016:1287