Bug 1514023
Summary: | Lots of WebSocket errors when logging out and logging in to the GUI | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Udi Kalifon <ukalifon> |
Component: | openstack-tripleo-ui | Assignee: | Honza Pokorny <hpokorny> |
Status: | CLOSED DUPLICATE | QA Contact: | Ola Pavlenko <opavlenk> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 12.0 (Pike) | CC: | beth.white, hpokorny, jjoyce, jpichon, jschluet, jtomasek, sclewis, slinaber, tvignaud |
Target Milestone: | Upstream M2 | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-07 06:39:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Udi Kalifon
2017-11-16 13:53:53 UTC
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 *** |