Bug 1724053
| Summary: | Log into Kibana console get "500 InternalError" | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> | |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.2.0 | CC: | aos-bugs, clasohm, nkim, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1765435 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:32:26 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: | ||||
| Bug Blocks: | 1765435 | |||
|
Comment 1
Qiaoling Tang
2019-06-28 02:16:46 UTC
Working from standing up a 4.1 cluster and then swapping in 4.2 images I was able to replicate the issue. The problem is the kibana-proxy oauthclient secret is not the same as the kibana-proxy secret oauth-secret. Deleting the oauthclient/kibana-proxy and secret/kibana-proxy forces the CLO to recreate the entries and the issue goes away. This may be the short term work around Fixed in https://github.com/openshift/cluster-logging-operator/pull/217 Tested by removing the file from the CLO pod which causes CLO to regen secrets. Delete the oauthclient/kibana-proxy, and wait until a new oauthclient/kibana-proxy created, then I can log into the Kibana console successfully. Verified with ose-cluster-logging-operator-v4.2.0-201907311819 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-2019:2922 |