MAAS Beta 1 UI enters unrecoverable state

[Bill Wear]

Created a KVM in MAAS Beta 1, took me to project page, selected default project, pressed green button. Result was the following error message:

Error: An unexpected error has occurred, please try refreshing your browser window.

Repeatedly tried refreshing with tail-f on the various log files. The only error logging linked to refresh occurred in regiond.log:

2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET /MAAS/r/kvm/10/project HTTP/1.1 --> 304 NOT_MODIFIED (referrer: -; agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0)
2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET /MAAS/r/root-application.855fff2c7d56185da545.js HTTP/1.1 --> 304 NOT_MODIFIED (referrer: http://192.168.86.91:5240/MAAS/r/kvm/10/project; agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0)
2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET /MAAS/r/475.30b9c258dcfcea078001.js HTTP/1.1 --> 304 NOT_MODIFIED (referrer: http://192.168.86.91:5240/MAAS/r/kvm/10/project; agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0)
2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET /MAAS/accounts/login/ HTTP/1.1 --> 200 OK (referrer: http://192.168.86.91:5240/MAAS/r/kvm/10/project; agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0)

Repeatedly refreshing the screen does not solve the problem.

[Bill Wear (billwear)]

restarting MAAS appears to work until you select the "KVM" screen again, when you enter the same infinite loop.

[Bill Wear (billwear)]

using the MAAS CLI to remove the vmhost successfully removes it. repeating the create attempt results in the same issue, though i have discovered that if i click on some tab other than KVM and refresh, the interface recovers. i can then click on the KVM tab and see the KVM i tried to create, but clicking on it results in another "refresh" infinite loop.

used MAAS CLI to remove the vmhost again, then tried creating one with the MAAS CLI itself: appears to work and UI recovers on next refresh, of course without the KVM (which was just deleted).

tried using MAAS CLI to create a KVM: i can create the lxd vmhost (although the "project" field, listed as "optional," is in fact required). as soon as i click on the vmhost name in the UI, i'm back into the infinite refresh loop.

ignored refresh issue and tried composing a machine using the MAAS CLI on this new lxd vmhost: this worked, so going back to UI, switching to machine tab and refreshing appears to show a new vm being commissioned normally. watched it walk through the commissioning steps until 50-maas..., where it failed with the following error:

--2021-04-07 21:01:30-- http://10.196.199.1:5248/machine-resources/amd64
Connecting to 10.196.199.1:5248... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-04-07 21:01:30 ERROR 404: Not Found.

may be a different bug.

[Bill Wear (billwear)]

problem remains after "snap refresh" to get MAAS up to Beta 2, although snap keeps volunteering the message, "consider a re-refresh of maas" every time. ??

[Bill Wear (billwear)]

note: when Lee and I were chasing bugs today, it became obvious that his freshly-built version (built this morning) didn't have this problem, while my Beta 2 version (released Wednesday) did. also, I have never been able to reproduce this behavior on bolla.

[Caleb Ellis (caleb-ellis)]

Hey Bill, are you able to see if you can reproduce this using the latest MAAS?

We did fix an issue recently that only seemed to occur on a `make sampledata` MAAS built from source, but couldn't reproduce it with the snap version. The error was related to trying to sort (and in Javascript land, mutate) the KVM's storage pools - did you see anything resembling that in the error message/browser console?

[Bill Wear (billwear)]

no, i didn't get that kind of return from the system, but i may not have
looked in the right place.

anyway, the Beta3 doesn't have this problem. up to you whether to keep
this bug open or not.

On Mon, Apr 19, 2021 at 7:00 PM Caleb Ellis <email address hidden>
wrote:

> Hey Bill, are you able to see if you can reproduce this using the latest
> MAAS?
>
> We did fix an issue recently that only seemed to occur on a `make
> sampledata` MAAS built from source, but couldn't reproduce it with the
> snap version. The error was related to trying to sort (and in Javascript
> land, mutate) the KVM's storage pools - did you see anything resembling
> that in the error message/browser console?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1922965
>
> Title:
> MAAS Beta 1 UI enters unrecoverable state
>
> Status in MAAS:
> New
> Status in maas-ui:
> New
>
> Bug description:
> Created a KVM in MAAS Beta 1, took me to project page, selected
> default project, pressed green button. Result was the following error
> message:
>
> Error: An unexpected error has occurred, please try refreshing your
> browser window.
>
> Repeatedly tried refreshing with tail-f on the various log files. The
> only error logging linked to refresh occurred in regiond.log:
>
> 2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET
> /MAAS/r/kvm/10/project HTTP/1.1 --> 304 NOT_MODIFIED (referrer: -; agent:
> Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101
> Firefox/87.0)
> 2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET
> /MAAS/r/root-application.855fff2c7d56185da545.js HTTP/1.1 --> 304
> NOT_MODIFIED (referrer: http://192.168.86.91:5240/MAAS/r/kvm/10/project;
> agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101
> Firefox/87.0)
> 2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET
> /MAAS/r/475.30b9c258dcfcea078001.js HTTP/1.1 --> 304 NOT_MODIFIED
> (referrer: http://192.168.86.91:5240/MAAS/r/kvm/10/project; agent:
> Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101
> Firefox/87.0)
> 2021-04-07 20:38:21 regiond: [info] 192.168.86.91 GET
> /MAAS/accounts/login/ HTTP/1.1 --> 200 OK (referrer:
> http://192.168.86.91:5240/MAAS/r/kvm/10/project; agent: Mozilla/5.0 (X11;
> Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0)
>
> Repeatedly refreshing the screen does not solve the problem.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1922965/+subscriptions
>

--
Bill Wear, MAAS Developer Advocate

[Caleb Ellis (caleb-ellis)]

I'm moderately confident it was the storage pool bug - complete UI crashes are pretty rare and that was one of them. We can reopen if we hit it again.

[Caleb Ellis (caleb-ellis)]

Relevant PR: https://github.com/canonical-web-and-design/maas-ui/pull/2507