Cannot load workpad into non-default space

[kibanamachine]

Original comment by @alexfrancoeur:

I've tried this a few times now. For some reason, you cannot upload spaces workpads into spaces that have been created. It works fine with the default space.

cc: @rashidkpc @w33ble

[kibanamachine]

Original comment by @alexfrancoeur:

Hmm, seems to be related to as well. They load, but they won't show on the page.

[alexfrancoeur]

@w33ble @rashidkpc spaces was just merged into master, we should be able to test this more easily now

[legrego]

I'm starting to look at this, FWIW

[alexfrancoeur]

Thanks Larry!

…

On Mon, Oct 8, 2018, 4:28 PM Larry Gregory ***@***.***> wrote: I'm starting to look at this, FWIW — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23168 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYA-f7T89O6ghbGOGE6t7lVTPyukKNMeks5ui28xgaJpZM4Woc8Z> .

[legrego]

So, it appears the root cause lies here.

We are deriving the socket endpoint based on chrome.getBasePath(). This returns the space-aware base path, rather than just the server.basePath path. Since socket.io is listening for a specific endpoint /socket.io, it won't be able to resolve paths like /s/marketing/socket.io.

Testing locally, I'm able to get canvas to work in a non-default space when I use just the server's base path to construct the socket URL, so I think this is the correct approach.

My problem is that I'm not sure of the best way to do this. Canvas exposes the server's base path via an exported UI app variable, but since the socket is initialized whenever the file is imported, that variable isn't available. We could add something to chrome to provide this, but that leaks the base path abstraction that spaces provides

[alexfrancoeur]

Nice, thanks Larry! @rashidkpc @w33ble any idea how we can best proceed here?

[w33ble]

Talked with @kobelb about this today. I proposed adding a chrome.getSocketPath() method, so we could attach the socket to one path that didn't change based on spaces. I'm assuming based on what I've heard from other people that we want a single socket server for Kibana that all apps will use, so any other app could use that method as well. It'll require upstream changes, obviously.

[sophiec20]

For extra info, I am seeing this and not using spaces.

• deployed locally from tar.gz
• spaces not configured / enabled
• trial license
• security enabled (elasticsearch.username and password)
• 6.5.0 { "build": { "hash": "566aaba", "date": "2018-10-15T13:05:56.081633Z" },

Discover tab is open and just sitting there. The error count in Console is rising. Approx 300 errors in 10 mins (ish).

[stacey-gammon]

Also noted here: #24087

Though I'm not sure if this is the same issue because Sophie's account, and the link above, are not related to using spaces?

[w33ble]

@sophiec20 You see the errors because the socket is always opened, even when you're not in Canvas. There's an issue for avoiding starting Canvas things until the user loads Canvas: #23379

Closing this issue will make the errors go away though.

Also, just as a follow up here, the error shows up because the socket server is listening on the basepath, but now that spaces hijacks that value, the client tries to connect to the basepath + space, hence the 404. If you hard-code the basepath on the client, everything works correctly with spaces.

So, as mentioned earlier, having a new method for the client to resolve the socket path (ie. uiChrome.getSocketPath()) would fix this.

[sophiec20]

Thanks @w33ble - I'll follow that ticket instead and leave you to your spaces.