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

Bug 1376080

Summary:	pick-up fix for Nexus threads prematurely terminating sessions
Product:	Red Hat OpenStack	Reporter:	caboucha
Component:	python-networking-cisco	Assignee:	Nir Magnezi <nmagnezi>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	8.0 (Liberty)	CC:	amuller, chrisw, jdonohue, mburns, mlopes, nyechiel, srevivo, tfreger
Target Milestone:	async	Keywords:	OtherQA, Triaged, ZStream
Target Release:	8.0 (Liberty)	Flags:	nmagnezi: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	hot
Fixed In Version:	python-networking-cisco-2.1.1-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, during port scaling, the ML2 plugin Nexus MD Driver threads closed the connections before other threads were completed. Consequently, the Nexus limit of 8 connections was exceeded. This update adds locks to threads, to prevent the thread from interfering with another thread's operations.	Story Points:	---
Clone Of:	1376063
Clones:	1376081 (view as bug list)		Environment:
Last Closed:	2016-12-21 16:44:23 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:	1376063, 1376465
Bug Blocks:	1194008, 1295530, 1376069, 1376073, 1376076, 1376077, 1376081, 1376086

Description caboucha 2016-09-14 15:32:25 UTC

Description of problem:
Please incorporate the Nexus MD ML2 Plugin Solution for OSP8:
https://review.openstack.org/#/c/358817/

There exists a neutron process with both a Nexus replay thread and a config thread. These threads share the same ssh session. When they are talking to Nexus at the same time, I saw one thread closing the nexus ssh session before the other thread was complete resulting in unexpected errors.

Version-Release number of selected component (if applicable):

How reproducible:
Very much so with scale and replay configured

Steps to Reproduce:
1. Scale Ml2 Port traffic
2. Replay configured in ml2_conf_cisco.ini file (switch_heartbeat_time = 30)
3.

Actual results:


Expected results:


Additional info:

Comment 9 errata-xmlrpc 2016-12-21 16:44:23 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-2988.html