Bug 1308385

Summary: Couldn't establish socket connection successfully on Chrome, Safari
Product: OKD Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: abhgupta, aos-bugs, jliggitt, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 17:13:28 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:
Attachments:
Description Flags
LogErrorInChrome none

Description Yadan Pei 2016-02-15 01:49:46 UTC
Created attachment 1127146 [details]
LogErrorInChrome

Description of problem:
In V3 STG env, always failed to get build log, deployment log and pod log,pod terminal.Reproduces on Chrome, Safari. Firefox43 and IE11 work well

Version-Release number of selected component (if applicable):
V3 STG

How reproducible:
Always

Steps to Reproduce:
1. Login to STG env on web console
2. Create application on web console
3. When in running status, watch build log, deployment log, pod log and pod terminal

Actual results:
3. Couldn't get these logs neither could access pod terminal on web console

Expected results:
3. Should watch log successfully and access pod terminal

Additional info:

Comment 1 Yadan Pei 2016-02-15 03:23:14 UTC
Version of Chrome and Safari:
Chrome 46
Safari 9

Comment 2 Jordan Liggitt 2016-02-15 14:44:17 UTC
I cannot recreate with Chrome 48. Websockets and build logs work fine.

Comment 3 Yadan Pei 2016-02-16 06:26:53 UTC
checked on Chrome 48, works fine as you said. 

How about Safari 9 on your side?

Comment 4 Jessica Forrester 2016-03-21 20:42:17 UTC
I just validated things are working on safari 9.  I think the certs may not have been set up yet on the server at the time this was reported (was still using self-signed certs).  Safari has a known issue with "accepting certs" not fully accepting the certs into the keychain so subsequent websocket requests don't work.  You can install the cert other ways and that allows it to work as expected.

Please double check it works for you as well now.

Comment 5 Yadan Pei 2016-03-22 01:12:01 UTC
Checked again, after trusting certificates on Safari, it works as expected