Console and Exec commands are not redirected to the correct host in a cluster
Opened this issue · 2 comments
When hosts are in a cluster, you can see all the containers from any of the hosts (which is good), but Exec and Console only work if you are on the container's actual host first.
Ex: If you select Host#1 in LXD Dashboard, then try to Console/Exec on a container running in the same cluster on Host#2, this message results:
--- Encrypted Connection Closed ---
Expected behavior: LXD dashboard should direct the Console/Exec operation to the host actually running the container, irrespective of the host currently in-focus in LXD Dashboard. (This is what the lxc command does)
Thank you - LXD Dashboard is excellent, I use it all the time.
Dave,
Thanks! Ah, this is an interesting issue. Thanks for taking the time to figure out what was going on. So yes, all instances from a cluster are listed on each host and I didn't consider that the websocket connection for console/exec might not work it the instance is located on a different host that what you are connected to. Good find. I will spend some time this weekend to see if I can find a workaround for this issue.
Hi Matthew, I have some maybe cosmetic but 'similar': If I have several browser tabs open and navigating to different "pages" (containers or overview and so on..) The (via ajax) loaded status in red on top is "global" - showing in every browser tab the same last "central" message.. Just saying that, to make you more headache :) anyhow, your software is a great thing! Please tell me, if I should move this to another ticket, maybe...