+++ This bug was initially created as a clone of Bug #1356019 +++ Description of problem: In 3.3 installed env, LOGO and DOC links are all ORIGIN specified Version-Release number of selected component (if applicable): openshift v3.3.0.4 openshift-ansible-3.3.1-1.git.2.57a2f34.el7.noarch How reproducible: Always Steps to Reproduce: 1. Install an ose-3.3 env with deployment_type=openshift-enterprise setting in ansible inventory 2. Check OSE 3.3 web console Actual results: 2. LOGO and DOC links are all pointing to ORIGIN Expected results: 2. OSE env should have everything customized as OpenShift Enterprise Additional info: --- Additional comment from Troy Dawson on 2016-08-02 05:48:04 CST --- This has been merged and is in OSE v3.3.0.13 or newer. --- Additional comment from Jessica Forrester on 2016-08-02 07:11:37 CST --- Only the oauth/login page changes have merged, the doc links and the logo within the console code aren't in yet. --- Additional comment from Jessica Forrester on 2016-08-15 21:10:59 CST --- This should all be fixed now --- Additional comment from Jessica Forrester on 2016-08-15 21:11:41 CST --- Also be aware the docs links will 404 since the rebranding of the URLs to container platform instead of enterprise hasn't gone live yet. --- Additional comment from on 2016-08-16 13:54:42 CST --- Checked against v3.3.0.19 LOGO in login/oauth is changed to OpenShift Container Platform DOC links are pointing to https://docs.openshift.com/container-platform/3.3/* The Logo and Links are right now, move to VERIFIED
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