Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1547263 - Kibana page displays "OPENSHIFT ORIGIN" in OCP
Kibana page displays "OPENSHIFT ORIGIN" in OCP
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.1
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.7.z
Assigned To: Jeff Cantrill
Anping Li
:
Depends On: 1546311
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-20 16:47 EST by Jeff Cantrill
Modified: 2018-04-05 05:40 EDT (History)
4 users (show)

See Also:
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 05:39:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:40 EDT

  None (edit)
Description Jeff Cantrill 2018-02-20 16:47:37 EST
+++ 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 3 Anping Li 2018-03-02 03:13:24 EST
Pass with openshift3/logging-kibana/images/v3.7.36-1
Comment 7 errata-xmlrpc 2018-04-05 05:39:53 EDT
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

Note You need to log in before you can comment on or make changes to this bug.