Bug 1376080 - pick-up fix for Nexus threads prematurely terminating sessions
Summary: pick-up fix for Nexus threads prematurely terminating sessions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-cisco
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: async
: 8.0 (Liberty)
Assignee: Nir Magnezi
QA Contact: Ofer Blaut
URL:
Whiteboard: hot
Depends On: 1376063 1376465
Blocks: 1194008 1295530 1376069 1376073 1376076 1376077 1376081 1376086
TreeView+ depends on / blocked
 
Reported: 2016-09-14 15:32 UTC by caboucha
Modified: 2019-09-10 14:08 UTC (History)
8 users (show)

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.
Clone Of: 1376063
: 1376081 (view as bug list)
Environment:
Last Closed: 2016-12-21 16:44:23 UTC
Target Upstream Version:
Embargoed:
nmagnezi: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 358817 0 None None None 2016-09-22 16:35:31 UTC
Red Hat Product Errata RHBA-2016:2988 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2016-12-21 21:35:02 UTC

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


Note You need to log in before you can comment on or make changes to this bug.