Bug 1694899 - The kibana was authorized as CN=system.logging.kibana by mistake
Summary: The kibana was authorized as CN=system.logging.kibana by mistake
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.11.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
Depends On: 1693957
TreeView+ depends on / blocked
Reported: 2019-04-02 02:20 UTC by Qiaoling Tang
Modified: 2019-06-06 02:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1693957
Last Closed: 2019-06-06 02:00:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0794 0 None None None 2019-06-06 02:00:39 UTC

Comment 1 Jeff Cantrill 2019-04-02 13:18:57 UTC
Are you actually seeing this issue with released code?  The change that identified this issue in 4.1 as part of porting from 3.11 due to https://bugzilla.redhat.com/show_bug.cgi?id=1666674 was never moved from 'MODIFIED' and reverted by https://github.com/openshift/openshift-ansible/pull/11445

Comment 2 Qiaoling Tang 2019-04-03 00:12:39 UTC
Yes, when using openshift-ansible-3.11.100 to deploy logging, the issue could reproduce, no problem when using openshift-ansible-3.11.98 to deploy logging

Comment 4 Anping Li 2019-04-16 07:46:53 UTC
The kibana work well with v3.11.104

Comment 6 errata-xmlrpc 2019-06-06 02:00:29 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.


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