Bottom line up front: I’ve broken my Kibana by attempting an upgrade from 7.12 to 7.14.
We have an Elastic Stack installation in a development sandbox environment. The first version of the Stack components installed in this enclave was 7.12, and I’ve been working in this enclave on a migration plan to take our production enclaves to 7.14. I read the suggested order for doing upgrades and started with the Elasticsearch nodes. 7.14 installed just fine on those, I restarted each, the cluster is happy and responding to curl from the command line.
I then moved to the Kibana node, and I naively did not read any of the other migration instructions. I’ve done upgrades in other test environments from, for example, 6.8 to 7.3 by simply stopping Kibana, installing the new version, and then restarting Kibana, and magically everything works. No such luck this time. The installation apparently went OK, though I did get a non-fatal squawk about the location of the keystore file, but there is no joy in trying to access the Kibana web page.
Instead I’m getting a page saying “Something went wrong Try refreshing the page. If that doesn’t work, go back to the previous page or clear your session data.” Refreshing the page and clearing the session doesn't change the response, which is a pinkish-bordered box with red text “kbnBundles does not have a module defined for “plugin/data/public””. Inside the border is the following:
Error: kbnBundles does not have a module defined for “plugin/data/public”
(ten lines similar to the “@https” and “__webpack” lines above)
I’ve restarted the Kibana node, and cleared my web browser (Firefox) cache. I haven’t installed any plugins, at least not as far as I know. Obviously Kibana is running, but not responding correctly. Any suggestions for troubleshooting would be appreciated.