Hide Forgot
Created attachment 1219248 [details] Cannot login on Edge and IE Description of problem: In Windows Edge 25 and IE 11, cannot login to registry console. Firefox, Chrome work. Version-Release number of selected component (if applicable): openshift v3.4.0.24+52fd77b cockpit 118 $ docker images | grep registry brew-pulp-...redhat.com:8888/openshift3/registry-console 3.3 445ef31dcaaf 2 days ago 223.8 MB This image id from 'brew' is just the one verified in https://bugzilla.redhat.com/show_bug.cgi?id=1373446#c8 How reproducible: Always Steps to Reproduce: 1. Login to registry console in Windows10 Edge 25 (or IE 11), input user/password. Actual results: 1. Cannot login. It always showing 'Validating authentication token' with spinning circle, see att. Expected results: 1. Can login Additional info: Also set up an env with following image from registry.ops. For this env, Edge can login bug IE cannot login. $ docker images | grep registry-console registry.ops..../openshift3/registry-console 3.3 f8a757a055c5 2 days 223.8 MB In thi env, though Edge can login, Edge still reproduces bug 1378810
Where can I get a container with openshift v3.4.0.24+52fd77b?
Patch merged upstream: https://github.com/cockpit-project/cockpit/pull/5350
Upstream master commits https://github.com/cockpit-project/cockpit/commit/b403d66ff9b2a74c58dc296236491af2aae33601 https://github.com/cockpit-project/cockpit/commit/80a239cf53d0eb44fef5da3e3b31d67bb065e336
FYI, today tested with new image: $ docker images | grep registry-console brew-pulp.../openshift3/registry-console 3.3 c6f41eb28dfa 3 days ago 224.8 MB Now the issue is not reproduced in Edge and IE
Fixed in cockpit 122-3 registry container image: openshift3/registry-console:3.3-5
Since the login issue has been fixed in cockpit 122-3, move the bug to Verified.
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. https://access.redhat.com/errata/RHBA-2016:2943