Bug 1396450

Summary: [atomic registry] Chrome cannot login to registry console when system proxy is set
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: Management ConsoleAssignee: Dominik Perpeet <dperpeet>
Status: CLOSED NOTABUG QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: high    
Version: 3.4.0CC: aos-bugs, jokerman, mmccomas, pvolpe, xxia
Target Milestone: ---   
Target Release: ---   
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: 2016-11-23 10:08:29 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:
Attachments:
Description Flags
Set-system-proxy-step1
none
Origin WS failure none

Description Xingxing Xia 2016-11-18 10:42:59 UTC 
Description of problem:
Chrome cannot login to registry console when System system proxy is set. Unset system proxy, it can login. The Chrome used is ver 54.
For Firefox, a bit complex, see more info below
See related attachments

As comparsion, console such as openshift console does not have the issue.

Version-Release number of selected component (if applicable):
cockpit 118

registry.ops..../openshift3/registry-console 3.3  f8a757a055c5  10 days ago    223.8 MB

How reproducible:
Always

Steps to Reproduce:
1. Set OS system proxy
2. Login to registry console with Chrome, input user/password.


Actual results:
2. A circle is spinning a while, then the login fails and page returns "Reconnect".

Expected results:
2. Should login successfully

Additional info:
For Firefox (version used is 49), in its Network setting:
If check the option "Manual proxy configuration", input proxy, the problem does not occur, Firefox can login to registry console.

If check the option "Use system proxy settings", and set OS system proxy, the problem occurs, Firefox can not login.
Comment 2 Xingxing Xia 2016-11-18 11:05:02 UTC 
Created attachment 1221817 [details]
Set-system-proxy-step1
Comment 8 Dominik Perpeet 2016-11-22 08:13:14 UTC 
Did your last attempt use a build with cockpit >= 122-3?

Does your proxy support WebSockets?
Comment 10 Peter 2016-11-22 16:57:01 UTC 
I think the proxy you are using doesn't support websockets. How are you testing the openshift console? Unlike cockpit only some parts of the openshift console use websockets, so you have to navigate around.

In my testing with your proxy settings, both cockpit and the parts of openshift that use websockets failed. You can see the failures in the network tab of chrome dev tools (see screen shot)
Comment 11 Peter 2016-11-22 16:57:47 UTC 
Created attachment 1222797 [details]
Origin WS failure
Comment 12 Xingxing Xia 2016-11-23 02:56:52 UTC 
Tried Origin websocket, got WS failure too. So seems the problem reported is not cockpit issue. May close it?
Comment 13 Dominik Perpeet 2016-11-23 10:08:29 UTC 
Thanks for verifying. I will close this as it's not a bug in Cockpit.