Debugging failed power scripts is hard

Bug #1012955 reported by Julian Edwards
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned

Bug Description

When a power script fails, you just get something like this:

PowerActionFail: virsh failed with return code 1

It would be nice if it showed the script invocation and its command line arguments.

Tags: provisioning
Changed in maas:
status: New → Triaged
importance: Undecided → High
tags: added: provisioning
Revision history for this message
Julian Edwards (julian-edwards) wrote :

And its output!

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.