Description of problem: When you log out of the GUI, and you have the console window (F12) open, you start seeing these errors: tripleo_ui.js:43 WebSocket is already in CLOSING or CLOSED state When you log back in you see the above message many more times. The GUI seems to be working, no noticeable implications result from this error, but with the console window open it is visible and looks serious. Version-Release number of selected component (if applicable): openstack-tripleo-ui-7.4.3-2.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Open the console window (F12). 2. Log out. 3. Log back in. Actual results: tripleo_ui.js:43 WebSocket is already in CLOSING or CLOSED state. t.default.sendMessage @ tripleo_ui.js:43(anonymous function) @ tripleo_ui.js:42(anonymous function) @ tripleo_ui.js:122l.value @ tripleo_ui.js:88(anonymous function) @ tripleo_ui.js:88l.value @ tripleo_ui.js:88(anonymous function) @ tripleo_ui.js:43a.value @ tripleo_ui.js:43t.(anonymous function) @ tripleo_ui.js:43(anonymous function) @ tripleo_ui.js:122e @ tripleo_ui.js:122(anonymous function) @ tripleo_ui.js:122(anonymous function) @ tripleo_ui.js:122c.dispatch @ tripleo_ui.js:122(anonymous function) @ tripleo_ui.js:38(anonymous function) @ tripleo_ui.js:122fetchPlans @ tripleo_ui.js:77s.value @ tripleo_ui.js:77e.notifyAll @ tripleo_ui.js:67p.close @ tripleo_ui.js:116a.closeAll @ tripleo_ui.js:42a.perform @ tripleo_ui.js:42a.perform @ tripleo_ui.js:42d.perform @ tripleo_ui.js:37k @ tripleo_ui.js:37E.close @ tripleo_ui.js:37a.closeAll @ tripleo_ui.js:42a.perform @ tripleo_ui.js:42d.perform @ tripleo_ui.js:37k @ tripleo_ui.js:37a.closeAll @ tripleo_ui.js:42a.perform @ tripleo_ui.js:42f.batchedUpdates @ tripleo_ui.js:116l @ tripleo_ui.js:37r @ tripleo_ui.js:47u.enqueueSetState @ tripleo_ui.js:47r.setState @ tripleo_ui.js:61s.handleChange @ tripleo_ui.js:119c @ tripleo_ui.js:69(anonymous function) @ tripleo_ui.js:122(anonymous function) @ tripleo_ui.js:122c.dispatch @ tripleo_ui.js:122(anonymous function) @ tripleo_ui.js:40i @ tripleo_ui.js:89(anonymous function) @ tripleo_ui.js:89u @ tripleo_ui.js:43 tripleo_ui.js:88 action @ 15:44:20.674 FETCH_WORKFLOW_EXECUTIONS_PENDING
Note that this issue happens only when 'zaqar' logger is enabled.
Apparently Zaqar logger tries to send messages even when Zaqar connection is closed instead of queuing messages. Message queuing happens only when Zaqar WebSocket connection is not initially established and once connection is authenticated, it flushes messages and starts sending them directly from that point. We need to add a mechanism which gets back to queuing messages when Zaqar WebSocket connection is closed.
I propose that close this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1507425
*** This bug has been marked as a duplicate of bug 1507425 ***