| Summary: | [atomic registry] In Windows Edge and IE, cannot login to registry console | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> | ||||
| Component: | Management Console | Assignee: | Dominik Perpeet <dperpeet> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.4.0 | CC: | aos-bugs, jokerman, mmccomas, pvolpe, stefw, tdawson, xxia, yanpzhan | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| 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-12-12 21:09:47 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
Xingxing Xia
2016-11-10 08:57:57 UTC
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 |