No feedback to user when cluster is not running

Bug #1341121 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Graham Binns

Bug Description

Commissioning is not working in the Garage MAAS with MAAS 1.6b4.

Credentials have been validated. Asking MAAS to commission the node does not turn on the node at all. No OOPS is generated. The node then stays in a "Commissioning" state indefinitely.

Tags: robustness

Related branches

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

Hmm... this time it seems the problem was that a celery daemon was silently not running.

Having parts of MAAS silently not running is very poor user experience - when it's broken it's useless but very difficult to know why that is.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Celery is being deprecated this cycle (for removal in a future release but we need to keep a window of RC/CC compatibility for now). When the internal bi-directional RPC is up and away, spotting dead clusters will be very easy.

tags: added: celery robustness
Changed in maas:
status: New → Triaged
importance: Undecided → High
summary: - Commissioning fails without error
+ No feedback to user when celery is not running
summary: - No feedback to user when celery is not running
+ No feedback to user when cluster is not running
tags: removed: celery
Revision history for this message
Raphaël Badin (rvb) wrote :

The fix for this is twofold:
- whether or not the clusters are connected is displayed on the cluster listing page.
- one gets instant feedback (a message in the UI, a 503 response in the API) when one tries to perform an action (like starting a node) when a cluster isn't connected.

Changed in maas:
milestone: none → 1.7.0
status: Triaged → Fix Committed
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 1341121] Re: No feedback to user when cluster is not running

It is not visible if I have to go into the cluster listing to see if
there is a problem! So, if any clusters / maas components are not
responding, then we should have an alert on the global header bar which
links to the more detailed listing of clusters and their statuses.

Mark

Revision history for this message
Christian Reis (kiko) wrote :

Graham, can you confirm that Mark's point has been addressed in 1.7?

Changed in maas:
assignee: nobody → Graham Binns (gmb)
Revision history for this message
Graham Binns (gmb) wrote :

On 2 October 2014 21:53, Christian Reis <email address hidden> wrote:
> Graham, can you confirm that Mark's point has been addressed in 1.7?

Sure.

Graham Binns (gmb)
Changed in maas:
status: Fix Committed → In Progress
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.

Other bug subscribers

Remote bug watches

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