Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1615293 - The kibana brand should be OpenshiftContainerPlatform
The kibana brand should be OpenshiftContainerPlatform
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.11.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.11.0
Assigned To: Lukas Vlcek
Anping Li
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2018-08-13 05:15 EDT by Anping Li
Modified: 2018-10-11 03:25 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:24:39 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)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin-aggregated-logging/pull/1303 None None None 2018-08-21 10:12 EDT
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:25 EDT

  None (edit)
Description Anping Li 2018-08-13 05:15:14 EDT 
Description of problem:
The logging-kibanna brand in the top left cornner is 'Openshift Origin'. It should be OpenshiftContainerPlatform



Version-Release number of selected component (if applicable):
Logging-kibana-v3.11.0-0.14.0.0

How reproducible:
always

Steps to Reproduce:
1. Deploy logging v3.11
2. Login kibana and check the brand

Actual results:
The kibana brand is Openshift Origin

Expected results:
The kibana is OpenshiftContainerPlatform
Comment 4 Anping Li 2018-08-23 07:03:37 EDT 
The bug have been fixed in ose-logging-kibana5/images/v3.11.0-0.20.0.0
Comment 6 errata-xmlrpc 2018-10-11 03:24:39 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:2652
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.