Bug 1388798
Summary: | LOGO and Docs links on OSE all pointed to ORIGIN | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> | |
Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.4.0 | CC: | aos-bugs, bleanhar, jforrest, jialiu, jokerman, mmccomas, pruan, sgoodwin | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: The logo and docs links must be changed for each release; it had not yet been completed.
Consequence: The logo and docs links were for Origin instead of OSE.
Fix: Added correct logo and docs links for the release.
Result: Logo and docs links are now correct for OSE.
|
Story Points: | --- | |
Clone Of: | 1356019 | |||
: | 1413823 (view as bug list) | Environment: | ||
Last Closed: | 2017-01-18 12:45:37 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: | ||||
Bug Depends On: | 1356019 | |||
Bug Blocks: | 1413823 |
Description
Yadan Pei
2016-10-26 08:21:25 UTC
Reproduces on v3.4.0.15 Yeah we have to rebrand every release unfortunately. Robb was just about to start working on this. I just opened https://github.com/openshift/origin-web-console/pull/740 to resolve. This has been merged into ose and is in OSE v3.4.0.17 or newer. Checked against v3.4.0.18+ada983f Now LOGO are changed to Openshift Container Platform And DOCs link to OCP https://docs.openshift.com/container_platform/3.4/* Move to VERIFIED Apologies. I prematurely closed this while adding doc text. moving back into 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-2017:0066 |