Bug 1833288
Summary: | Kibana OAuth HTTP 500 error - x509: certificate signed by unknown authority | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | rdomnu |
Component: | Logging | Assignee: | Periklis Tsirakidis <periklis> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | aos-bugs, awyatt, bsawyers, cruhm, fshaikh, jmalde, jniu, jnordell, mfuruta, nnosenzo, ocasalsa, periklis, qitang, rh-container, sgarciam |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 4.4.z | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Cluster-logging-operator did not reconcile the injected CA Bundle contents for fluentd. Same applies to elasticsearch-operator for kibana.
Consequence:
Fluentd and Kibana missing volume mounts to config maps with injected CA bundle
Fix:
Fetch anew the config map contents during reconciliation to ensure volume mounts.
Result:
Fluentd and Kibana mount the CA bundle config maps appropriately and certification works again
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-07 10:05:59 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: | 1834311 | ||
Bug Blocks: |
Description
rdomnu
2020-05-08 10:33:09 UTC
Just another comment: After reverting to the Subscription/CSV version 4.3 and reinstalling cluster logging, the ca bundle configmap is mounted to Kibana deployment and authentication works *** Bug 1838770 has been marked as a duplicate of this bug. *** Manually mounting the volume should just work as a workaround: https://access.redhat.com/solutions/5000761 verified on clusterlogging.4.4.0-202005301254 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-2020:2445 |