Bug 1835903
| Summary: | Kibana 6 index needs to be re-indexed on updated 4.4 to 4.5 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Periklis Tsirakidis <periklis> |
| Component: | Logging | Assignee: | Periklis Tsirakidis <periklis> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5 | CC: | anli, aos-bugs, jcantril |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
Updating the cluster logging stack from 4.4 to 4.5 needs a manual migration of the kibana index from 5to 6.
Consequence:
Without a live migration Kibana 5 pods are replaced with Kibana 6 pods that remain in CBLO.
Fix:
Live migration of the kibana 5 index to a kibana 6 index.
Result:
Kibana 6 pods start up w/o issues.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:39:04 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 1832849 has been marked as a duplicate of this bug. *** Move to verify as the Kibana can be started. A new issue, the Kibana couldn't be authorized from Oauth proxy. File a new bug https://bugzilla.redhat.com/show_bug.cgi?id=1842452. 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:2409 |
Description of problem: The upgrade process of cluster-logging from 4.4 to 4.5 fails to start kibana 6 after elasticseach migration. Kibana 6 stays in CrashloopBackoff due to: #The following values dynamically added from environment variable overrides: Using NODE_OPTIONS: '--max_old_space_size=368' Memory setting is in MB {"type":"log","@timestamp":"2020-05-14T17:07:28Z","tags":["fatal","root"],"pid":120,"message":"Error: Index .kibana belongs to a version of Kibana that cannot be automatically migrated. Reset it or use the X-Pack upgrade assistant.\n at assertIsSupportedIndex (/opt/app-root/src/src/server/saved_objects/migrations/core/elastic_index.js:246:15)\n at Object.fetchInfo (/opt/app-root/src/src/server/saved_objects/migrations/core/elastic_index.js:52:12)"} FATAL Error: Index .kibana belongs to a version of Kibana that cannot be automatically migrated. Reset it or use the X-Pack upgrade assistant. Version-Release number of selected component (if applicable): cluster-logging-operator- 4.5.0 elasticsearch-operator-4.5.0 How reproducible: Every time Steps to Reproduce: 1. Install cluster-logging 4.4 from marketplace 2. Trigger update to 4.5 3. Actual results: Kibana in CBLO Expected results: Elasticsearch-Operator to trigger reindexing of kibana index. Kibana starts without errors. Additional info: