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):
Steps to Reproduce:
1. Press F12 to see the console output
2. Log out and back in
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
*** Bug 1514023 has been marked as a duplicate of this bug. ***
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.