Bug 1832849
| Summary: | The kibana couldn't be migrated automatically | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED DUPLICATE | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.5 | CC: | aos-bugs |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-15 21:13:03 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: | |||
The kibana pod started after DELETE the .kibana index @Anping please define the order in which you upgraded the operators and whether it works if you swap. This may be a transient issue we recover from and simply need to document accordingly. That is the EO First upgrade. *** This bug has been marked as a duplicate of bug 1835903 *** |
Description of problem: #oc logs -c kibana kibana-86c9cd6bc8-trdrg #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-07T11:48:31Z","tags":["fatal","root"],"pid":119,"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): 4.5 How reproducible: always Steps to Reproduce: 1. Deploy Clusterlogging 4.4 2. Upgrade clusterlogging to 4.5 Actual results: #oc get pods --selector component=kibana NAME READY STATUS RESTARTS AGE kibana-86c9cd6bc8-trdrg 1/2 CrashLoopBackOff 6 9m9s Expected results: kibana can be upgraded automatically