Bug 1486748 - websocket.WebSocketBadStatusException seen in OSP12 ODL Cluster Setup
Summary: websocket.WebSocketBadStatusException seen in OSP12 ODL Cluster Setup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 12.0 (Pike)
Assignee: Josh Hershberg
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-30 13:00 UTC by Sridhar Gaddam
Modified: 2018-10-18 07:20 UTC (History)
3 users (show)

Fixed In Version: python-networking-odl-11.0.1-0.20171017155938.a0cb8d9.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-12-13 21:59:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1714160 0 None None None 2017-09-26 21:14:42 UTC
OpenStack gerrit 502967 0 None None None 2017-09-26 21:15:05 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Sridhar Gaddam 2017-08-30 13:00:30 UTC
Description of problem:

Setup: ODL HA Clustered Setup
3 Controllers running neutron servers + ODL Controller.
3 Compute nodes.

In OSP12 ODL Clustered setup, we noticed the following exception in neutron server logs.

Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: File "/usr/lib/python2.7/site-packages/networking_odl/common/websocket_client.py", line 114, in run...et_thread│················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: ws = self._connect_ws()                                                                                        │················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: File "/usr/lib/python2.7/site-packages/networking_odl/common/websocket_client.py", line 262, in _connect_ws    │················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: ws = self._socket_create_connection(stream_url)                                                                │················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: File "/usr/lib/python2.7/site-packages/networking_odl/common/websocket_client.py", line 242, in _so...onnection│················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: except websocket.WebSocketBadStatusException:                                                                  │················
Aug 30 07:33:01 overcloud-controller-2 neutron-server[98879]: AttributeError: 'module' object has no attribute 'WebSocketBadStatusException'                                 │················
Aug 30 09:22:57 overcloud-controller-2 neutron-server[98879]: /usr/lib64/python2.7/site-packages/sqlalchemy/orm/persistence.py:964: SAWarning: DELETE statement o... warning.│················
Aug 30 09:22:57 overcloud-controller-2 neutron-server[98879]: (table.description, expected, rows_matched)

IMO, there are two ways to fix the issue. Either we bump the python-websocket-client package on RHEL7.4 or avoid using the WebSocketBadStatusException status in networking-odl.

Version-Release number of selected component (if applicable):
The following packages were used when the issue was reproduced.
python-websocket-client-0.32.0-116.el7.noarch 
python-neutron-11.0.0-0.20170807223712.el7ost.noarch
python-networking-odl-11.0.0-0.20170806093629.2e78dca.el7ost.noarch

Comment 1 Josh Hershberg 2017-08-30 14:05:57 UTC
Fix proposed upstream: https://review.openstack.org/#/c/499115/

Comment 2 Josh Hershberg 2017-08-31 05:31:50 UTC
upstream bug
https://bugs.launchpad.net/ubuntu/+source/networking-odl/+bug/1714160

Comment 4 Itzik Brown 2017-11-05 09:41:26 UTC
I don't see an exception with:
python-networking-odl-11.0.1-0.20171017155938.a0cb8d9.el7ost.noarch

Comment 7 errata-xmlrpc 2017-12-13 21:59:22 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/RHEA-2017:3462


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