MAAS

Event log entries for Failed Deployment (and other failed stages) don't indicate reason for failure

Bug #1382663 reported by Jason Hobbs
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

The event log entry for a node transitioning to Failed Deployment is: Node changed status — From 'Deploying' to 'Failed deployment'. It would be a lot more useful if there was a reason given for the failed deployment.

Tags: hyperscale
Christian Reis (kiko)
Changed in maas:
milestone: none → next
Julian Edwards (julian-edwards)
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Christian Reis (kiko) wrote :

Is that reason easy to glean, though?

Changed in maas:
milestone: next → 1.7.1
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 1.7.1 → 1.7.2
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 1.7.2 → 1.7.3
Revision history for this message
Sean Feole (sfeole) wrote :

Tagging hyperscale to this bug, we see this quite a bit in the lab, but not much information about the failure in the maas logs.

tags: added: hyperscale
Andres Rodriguez (andreserl)
Changed in maas:
importance: High → Wishlist
milestone: 1.7.3 → next
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Björn Tillenius (bjornt)
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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