login redirect appears broken

[Ian Booth]

I am trying to go directly to a particular model via a URL like

https://10.124.114.24:17070/gui/8f501a98-51ed-4a44-84e5-19600b7d73ec/u/admin/controller

It takes me to the login page

https://10.124.114.24:17070/gui/8f501a98-51ed-4a44-84e5-19600b7d73ec/login/u/admin/controller

But then after I log in, I get redirected to some other model, usually "default"

https://10.124.114.24:17070/gui/8f501a98-51ed-4a44-84e5-19600b7d73ec/u/admin/default

I would have expected to get to the model I requested via the initial URL.

[Francesco Banconi (frankban)]

Hey Ian, thanks for reporting this.
So, GUI bugs are filed at <https://github.com/juju/juju-gui/issues>. In this case though, I just retargeted this to Juju as the issue must be solved on Juju itself.
With the newly released GUI URLs, I think it would be ok to drop the model UUID fragment of the path of the GUI served by Juju. We could
- make the GUI live at "https://{controller-addr}:17070/gui/" (so that model specific path would be "/gui/u/admin/default", "/gui/u/frankban/mymodel" etc);
- prevent the Juju handler from providing a model UUID in the config.js it dynamically generates (the path will be used in that case by the GUI) or provide the UUID corresponding to the requested path. The GUI implements this logic already.
At that point, refreshing on a model different than the initial one will work, and, moreover, refreshing after deleting the initial model will be less surprising.

[Jeff Pihach (hatch)]

Hi Ian, The issue you're seeing is actually known in the latest GUI (2.3.0). Here is the link to the issue that you can 'watch' for updates: https://github.com/juju/juju-gui/issues/2430. While a fix won't make it into the next release (2.4.0) it is on deck for the following release.

[Francesco Banconi (frankban)]

This has been fixed in https://github.com/juju/juju/pull/6992