Description of problem: As the summary states, HTML5 console does not connect to VM on very first attempt or sometimes if you close the Tab containing the Running Console(maybe by mistake) and then if you try to reopen the console for same VM again immediately, it may fail to connect. Version-Release number of selected component (if applicable): 5.8.0.16, but this behavior was noticed in previous builds too How reproducible: Not sure, intermittently maybe Steps to Reproduce: 1.Open HTML5 Console for any VM Actual results: May or may not connect to VM, you may see that on bottom left corner it may say Connected, but it might not show anything but a blank window, or may say disconnected. Please refer to screenshots for more info. Expected results: HTML5 console should behave consistently and it should connect to console all the time or show some more meaningful error text if there is an error. Additional info: If this bug can't be reproduced and solved, it should be noted in our official documentation as known issue. When HTML5 console connects without errors that are mentioned above, it works fine and you can use your mouse and keyboard to interact with it normally.
Created attachment 1282046 [details] HTML5 Console Connected but not Visible
Created attachment 1282047 [details] HTML5 Console Disconnected
I am thinking this is a duplicate of the websockets issue.... bug 1404354 Please close if you agree fellas. I believe this can be done by running the following. If you see more than a few of this processes, it'll cause problems with the connections. The more you see, the more likely connections will fail... [root@cfme ~]# netstat -napo | grep 5000 tcp 0 0 127.0.0.1:5000 0.0.0.0:* LISTEN 3017/puma 3.3.0 (tc off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:35048 TIME_WAIT - timewait (55.25/0/0) tcp 190 0 127.0.0.1:35080 127.0.0.1:5000 ESTABLISHED 48715/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:34936 TIME_WAIT - timewait (44.73/0/0) tcp 0 0 127.0.0.1:57724 127.0.0.1:5000 CLOSE_WAIT 35049/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:35082 ESTABLISHED 3017/puma 3.3.0 (tc off (0.00/0/0) tcp 304 0 127.0.0.1:35078 127.0.0.1:5000 ESTABLISHED 14821/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:35080 ESTABLISHED 3017/puma 3.3.0 (tc off (0.00/0/0) tcp 0 0 127.0.0.1:57524 127.0.0.1:5000 CLOSE_WAIT 35801/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:35082 127.0.0.1:5000 ESTABLISHED 15223/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:57784 127.0.0.1:5000 CLOSE_WAIT 23699/httpd off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:35088 ESTABLISHED 3017/puma 3.3.0 (tc off (0.00/0/0) tcp 0 0 127.0.0.1:5000 127.0.0.1:35078 ESTABLISHED 3017/puma 3.3.0 (tc off (0.00/0/0) tcp 114 0 127.0.0.1:35088 127.0.0.1:5000 ESTABLISHED 51971/httpd off (0.00/0/0)
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
Hey Dave, I will close it since it can not be reproduced consistently. It was about Occasionally getting "502 Error" Page when launching HTML5 Console. Also websocket workaround might have helped this improve.