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
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 ***