Clicking on model name results in "Something has gone wrong"

[ianmjones]

Describe the bug
Version Juju 2.8-rc2 (snap) / Dashboard 0.1.3 (beta)

When I click the name of my non-controller model in the Models area, in this case "gm-dev"...

... I get the following error message...

This happens every time, above screenshot includes devtools console in case that helps.

This was with an upgrade from 2.7.6 to 2.8-rc2, following upgrade guide from https://discourse.juju.is/t/juju-2-8-rc2-release-notes/3061, which had no problems. Then running juju upgrade-gui to pick up new dashboard.

The gm-dev model is a simple deploy of https://github.com/dshcherb/cockroachdb-operator on LXD with no real use as such but all seems to be working fine.

To Reproduce
Steps to reproduce the behaviour:

1. Go to Models area of dashboard.
2. Click on model name other than "controller"
3. Boom!

Expected behaviour
After clicking on the model I'd expect to see something not unlike I see for the controller model...

Desktop (please complete the following information):

• OS: Elementary 5.1
• Browser Firefox 76.0.1

Of note, whenever I refresh the dashboard I have to log in again.

[hatched]

Thanks for filing this issue, I'll have to deploy this to see if I can reproduce locally because unfortunately that error message isn't very helpful :)

The issue about logging in after refresh is being tracked here: #477 I'm going to try and prioritize this in the next month.

[hatched]

I believe I've resolved this issue in #520, once that lands I'll create a new release for Juju to see if it resolves it for you.

[hatched]

A new version has been released, 0.1.6 beta.

To upgrade:

• juju upgrade-dashboard && juju dashboard

If you wouldn't mind checking to see if this resolves the issue in viewing your model.

[ianmjones]

Thanks @hatched, but unfortunately same result on both Firefox 76 and Chromium 81.

But the fix ups for layout are looking good...

[ianmjones]

Just to double check stuff, I added a new gm-dev-pg model and deployed postgresql, worked fine ...

Then I deployed that same cockroachdb-operator charm with 3 units to the model, link no longer worked.

After removing the 3 cockroachdb units, still didn't work, but once I removed the cockroachdb application from the model, I could get to the model again.

Then I stayed on that working model page with just postgresql, and deployed cockroachdb to see what would happen. Sure enough, within a few seconds, as soon as the machine was up, got the "Something has gone wrong..." error.

Once I removed the cockroachdb application again, as expected the page didn't magically fix itself, but as soon as I refreshed and logged in again the model was available for view.

I'm guessing this is related to either a problem with the cockroachdb-operator charm, but more likely, I suspect it's because the charm is not available on the store.

There's a 404 error message related to grabbing the icon.svg visible in my previous post's Chromium screenshot that I expect is relevant.

[hatched]

That was my thought as well, in testing I had resolved one 'local charm' issue which was why I thought it was resolved. I'll be working on this this afternoon and hopefully get a fix out today.

[hatched]

@ianmjones I believe I've now finally resolved this issue :-)

0.1.7 has been released and you can give it a try by running juju upgrade-dashboard. I'd be interested to know if this resolves this issue for you.

[ianmjones]

@hatched yup, works for me, thank you!