Bug 1488076

Summary: Logo and docs links on OCP all point to ORIGIN
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas, rhamilto, sgoodwin, yapei
Target Milestone: ---Flags: rhamilto: needinfo-
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: 1413823
: 1559735 (view as bug list) Environment:
Last Closed: 2017-11-28 22:09:17 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:    
Bug Blocks: 1559735    

Description Xingxing Xia 2017-09-04 09:16:17 UTC 
+++ This bug was initially created as a clone of Bug #1413823 +++

+++ This bug was initially created as a clone of Bug #1388798 +++

+++ This bug was initially created as a clone of Bug #1356019 +++

Description of problem:
Logo and docs links on OCP all point to ORIGIN
Just a regular issue when beginning test new 3.x

Version-Release number of selected component (if applicable):
v3.7.0-0.123.0

How reproducible:
Always

Steps to Reproduce:
1. Install v3.7 OCP env
2. Login to web console, check top logo, check doc links

Actual results:
2. Logo and docs links on OCP all point to ORIGIN

Expected results:
2. Point to OCP related things.

Additional info:
Comment 1 Robb Hamilton 2017-09-05 18:19:07 UTC 
PR to resolve: https://github.com/openshift/origin-web-console/pull/2013
Comment 2 Xingxing Xia 2017-09-18 08:57:03 UTC 
Checked in v3.7.0-0.126.4, issue is fixed, now Logo is OPENSHIFT CONTAINER PLATFORM, docs links point to .../container-platform/3.7/...
Please move to ON_QA if no other concern, thanks
Comment 6 errata-xmlrpc 2017-11-28 22:09:17 UTC 
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/RHSA-2017:3188