node view does not refresh after commissioning

[Dimiter Naydenov]

I'm using maas - 1.8.0~alpha1+bzr3489+3488+348~ppa0~ubuntu14.04.1 from https://launchpad.net/~rvb/+archive/ubuntu/maas and while recommissioning all my 4 KVM nodes all at once I've noticed an error while trying to bootstrap a node with juju (tip of latest master):

2015-03-03 18:22:04 ERROR juju.cmd supercommand.go:430 failed to bootstrap environment: cannot start bootstrap instance: getInstanceNetworkInterfaces failed: cannot parse lshw XML details for node "/MAAS/api/1.0/nodes/node-4ea330be-c164-11e3-8a4b-525400355a63/": EOF

This deserves a separate juju-core bug, which I'll file later. However, since all nodes were recommissioned yesterday I wondered why the lshw output was missing, as all of them had one before. Let's check it out:

[maas-trusty] (master) dimitern@kubrik:~/work/juju-core$ maas maas-root node details -d node-4ea330be-c164-11e3-8a4b-525400355a63 detail_type=lshw
200 OK

   Content-Location: http://192.168.50.2/MAAS/api/1.0/nodes/node-4ea330be-c164-11e3-8a4b-525400355a63/?op=details&detail_type=lshw
       Content-Type: application/bson
               Date: Tue, 03 Mar 2015 18:26:27 GMT
             Server: TwistedWeb/13.2.0
             Status: 200
  Transfer-Encoding: chunked
               Vary: Authorization,Cookie
    X-Frame-Options: SAMEORIGIN

alldpF<?xml version="1.0" encoding="UTF-8"?>
<lldp label="LLDP neighbors"/>

No lshw output. Out of 4 nodes (512 MB RAM + 1 core per machine, 1 GB for the KVM running the MaaS cluter controller, 3.5 GB otherwise allocated on the amd64 trusty host, out of 8 GB RAM, 4 core i3 M 350 CPU - perhaps under load lshw times out or something) only two had lshw output. I've recommissioned the other two one by one, using the web UI (now with auto-updating in some of the views) - node state changed to Commissioning, the "9 output files" from the previous commissioning disappeared, as a few other details. Node got recommissioned and shut down, however the node view in the web UI did not update to show that (IIRC some of the page - like the log did update).

As MaaS is moving towards more dynamic, smart web UI which auto-updates it's reasonable to expect a consistent UX, not spotty.

This is more of a wishlist type of request, but a useful improvement nevertheless.

[Blake Rouse (blake-rouse)]

Your speaking of the node details page. We have just started replacing the node details page with the new design and live updating. The version you are using does not have this feature yet.