No instant feedback when performing an action in the UI

Bug #1437231 reported by Raphaël Badin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Richard McCartney

Bug Description

When performing a bulk action such as commissioning a bunch of nodes or an individual action such as commissioning just one node, there is no *instant* feedback after clicking the "Go" button.

As soon as the server starts processing the websocket requests there is feedback (the node's status are updated) but, especially over a slow network, this can take several seconds. During that time, it's easy to be confused about whether or not the action is being processed. What I'd like to see is a client-side feedback that would tell me that the action is being processed: the button could change its color, a spinning cog could appear, anything as long as there is a visual cue that something is happening behind the scenes. I think the user experience would be vastly improved by something as simple as this because it would fell much more responsive.

Tags: ui

Related branches

Changed in maas:
status: New → Confirmed
assignee: nobody → Carla Berkers (carlaberkers)
Revision history for this message
Carla Berkers (carlaberkers) wrote :

Hi Raphael,

I'm not an expert on websockets, can you let me know if my wording is correct:

CASE: when user clicks "Go"
MESSAGE: "Connecting to region controller" (do we have to say "through websocket" or is this implied?)

CASE: if MAAS isn't able to establish a connection
"Unable to [name of action] as connection to region controller cannot be established. Make sure your port configuration is correct "

When connection to server is established, the node status should change and the "connecting... " message should disappear
Can this all happen at the same time or can there be a delay between feedback from the websocket and the status of the node changing?

Thanks,
Carla

Revision history for this message
Raphaël Badin (rvb) wrote :

No, the websocket connection is establish once and for all when you first load the node listing page. After that, this connection is used to exchange messages back and forth. Of course the connection can drop but it should be re-established transparently as soon as possible.

So really the websocket connection is established at all times.

But what I was suggesting here is a kind of visual cue that the action has been recorded (the only pre-flight check can be: is the connection established —the check is instantaneous).

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Carla,

He is speaking of once you click go we should show progress of what is occurring. I am thinking in the bulk action dropdown we show progress of the action. Example text below.

"3 of 10 have started deploying"

this would count up until all have started

"9 of 10 have started deploying"

and then once all have started deploying then the message and dropdown go away. Now if one fails to start we should show a message as well, just like we now do on the node details page in the dropdown.

"""
2 of 10 have failed to deploy
    node-name.maas: error message
    other-node.maas: error message
"""

I think that would help show the user what is happening and show errors if any occur.

Changed in maas:
importance: Medium → High
milestone: none → next
Revision history for this message
Carla Berkers (carlaberkers) wrote :

See attached a journey that should solve this bug and your other questions around error styling.

Let me know if that works!

Changed in maas:
assignee: Carla Berkers (carlaberkers) → nobody
Changed in maas:
milestone: next → 1.8.0
Changed in maas:
status: Confirmed → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
assignee: Blake Rouse (blake-rouse) → Richard McCartney (ricgard)
Revision history for this message
Carla Berkers (carlaberkers) wrote :

Filed a new bug for parts of this design we can't implement for 1.8: https://bugs.launchpad.net/maas/+bug/1454132

Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.