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

Bug 1703467

Summary:	ML2/OVS - create port by ovs agent is very slow when there is many ports on same compute node
Product:	Red Hat OpenStack	Reporter:	Slawek Kaplonski <skaplons>
Component:	openstack-neutron	Assignee:	Nate Johnston <njohnston>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Eran Kuris <ekuris>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	amuller, ccamposr, chrisw, njohnston, ralonsoh, scohen
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-25 20:51:06 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:

Description Slawek Kaplonski 2019-04-26 14:10:47 UTC

Description of problem:
In case when on one compute node there is many ports which are using same security group and this security group uses rule to allow traffic from ports with given SG adding new port to host is very slow.
We tested it on compute with 170 trunk supports and it took about 5 minutes for new port to become ACTIVE.

In environment with OpenShift deployed on top of OpenStack 170 subports isn't a lot. It has to scale for much higher numbers.


How reproducible:
Always


Steps to Reproduce:
1. Create a lot of ports/trunk subports which uses same SG on one compute node
2. Add new port/subport to this compute after some time

Actual results:
New port will become active after couple of minutes as all existing ports will be "updated" due to changes in SG


Expected results:
Port should be ACTIVE almost immediately.

Additional info:

Comment 5 Nate Johnston 2019-12-02 20:51:24 UTC

*** Bug 1749962 has been marked as a duplicate of this bug. ***