Bug 1547263

Summary:	Kibana page displays "OPENSHIFT ORIGIN" in OCP
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.1	CC:	anli, aos-bugs, nschuetz, rmeggins
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The container image was not built with the required header image Consequence: Fix: Replace the origin header image with the OCP header image. Result: The Kibana page displays the desired header	Story Points:	---
Clone Of:	1546311	Environment:
Last Closed:	2018-04-05 09:39:53 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:	1546311
Bug Blocks:

Description Jeff Cantrill 2018-02-20 21:47:37 UTC

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

Description of problem:
Kibana page displays "OPENSHIFT ORIGIN" in the upper left hand corner on OpenShift Container Platform.

Version-Release number of selected component (if applicable):

openshift v3.7.23

How reproducible:

Always

Steps to Reproduce:
1. Open the web console and dig into a pod. Then click on Logs > View Archive.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Cantrill 2018-02-21 02:49:48 UTC

https://github.com/openshift/origin-aggregated-logging/pull/966

Comment 3 Anping Li 2018-03-02 08:13:24 UTC

Pass with openshift3/logging-kibana/images/v3.7.36-1

Comment 7 errata-xmlrpc 2018-04-05 09:39:53 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/RHBA-2018:0636