Bug 1507425 – When logging out and in again, you get: WebSocket is already in CLOSING or CLOSED state

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1507425 - When logging out and in again, you get: WebSocket is already in CLOSING or CLOSED state

Summary:	When logging out and in again, you get: WebSocket is already in CLOSING or CL...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-ui (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	Upstream M3
Target Release:	13.0 (Queens)
Assigned To:	Honza Pokorny
QA Contact:	Udi
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Duplicates:	1514023 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-30 04:57 EDT by Udi
Modified:	2018-06-27 09:39 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	openstack-tripleo-ui-8.3.1-0.20180303225336.57e3d96.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-06-27 09:38:59 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1746583	None	None	None	2018-01-31 14:30 EST
OpenStack gerrit	539642	None	master: MERGED	tripleo-ui: Stop logging over websocket on logout (Iaf365d78cf5e2b35c4f035a9f068266131940553)	2018-03-21 09:40 EDT
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:39 EDT

Groups: None (edit)

Description Udi 2017-10-30 04:57:46 EDT

Description of problem:
You see this error in the console when logging out and back in to the director ui:

ZaqarWebSocketService.js:95 WebSocket is already in CLOSING or CLOSED state.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.4.3-0.20171023133305.8616195.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Press F12 to see the console output
2. Log out and back in

Comment 4 Jiri Tomasek 2018-01-31 11:01:11 EST

This error happens when user is logged out. At that point, app disconnects from zaqar websocket and logger still tries to send messages. At that point we need to switch to storing the messages and flush them once user logs back in

Comment 5 Udi 2018-02-07 01:39:42 EST

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

Comment 8 Udi 2018-04-04 07:24:46 EDT

Verified: openstack-tripleo-ui-8.3.1-2.el7ost.noarch

Comment 10 errata-xmlrpc 2018-06-27 09:38:59 EDT

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-2018:2086

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