Kibana: Canvas - aeroelastic store exception

[mikehowey1]

Kibana version:
6.5.2
Elasticsearch version:
6.5.2
Server OS version:
Ubuntu
Browser version:
Chrome 70.0.3538.77
Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:
Get message after creating a workpad and selecting it to begin editing.
Steps to reproduce:
1.
2.
3.

Expected behavior:

Screenshots (if relevant):

Errors in browser console (if relevant):
Version: 6.5.2
Build: 18828
Error: Uncaught Error: An aeroelastic store should exist for page page-d6362a01-51f0-497c-be53-1528194a8fa3 (https://kibanadev/bundles/vendors.bundle.js:208)
at window.onerror (https://kibanadev/bundles/commons.bundle.js:3:859249)
Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/kibana-canvas

[w33ble]

This is reportedly still a problem in 6.5.3 too.

[eskibars]

Happened to me on 6.5.3 as @w33ble mentioned. My browser is different (Chrome 71.0.3578.98 64-bit on OSX)

[monfera]

@mikehowey1 thanks for the report! I'm looking at a v6.5.3 instance which I think hasn't changed in this area, couldn't reproduce it immediately. What's meant by _creating a workpad and selecting it to begin editing_? When I create a workpad, it immediately gets selected for editing, ie. there's no selection step, or is it different on your instance?

[w33ble]

@eskibars made it sound like just opening a workpad from the home screen will trigger this. I downloaded 6.5.4 of the stack and I'm not able to reproduce, but I'd like to add a proxy into the mix to slow things down and try again. I suspect this is an issue that comes up with increased latency.

@mikehowey1 can you give us any details about your setup? For example, are you running the whole stack on your computer, or is everything hosted on another box that you're just loading in your local browser? If it's another box, is it in the same building, or located elsewhere (data center, aws, etc)? And are Kibana and Elasticsearch on the same machine?

[monfera]

As a secondary topic, I'd be interested in how the error was worked around, ie. via a single page reload, or needed to create a new workbook, was there any significant data loss

[eskibars]

For me: I had created the workpad previously (and had it open in another tab -- didn't realize that). The workpad was in a Kibana Space that I created on 6.5. I got the error going to Kibana --> Select my Space --> Canvas --> Open my workpad. It's an internal to Elastic instance that I can point anyone at Elastic to if they want to explore. I do frequently get websocket timeouts on this instance.

Simply reloading the page seemed to fix the error for me.

[mikehowey1]

@w33ble The kibana and elastic data nodes are on separate hosts but in the same on-prem datacenter. The issue seems to have resolved itself however we have resolved a few websocket issues along the way also.

[monfera]

Thanks @mikehowey1, I'll close the issue for now, please reopen this w/ a comment if you run into the same situation.