If a power script fails, there is no UI feedback
Bug #1012954 reported by
Julian Edwards
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Raphaël Badin |
Bug Description
This is currently by design so this is a reminder bug to fix this.
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: notifications ui |
Changed in maas: | |
importance: | Low → High |
tags: | added: robustness |
tags: | added: landscape |
tags: | added: cloud-installer |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
assignee: | nobody → Raphaël Badin (rvb) |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Two failure modes we hit while demoing at intel:
a) the script fails (wrong credentials for instance)
b) The power command hits a timeout contacting the BMC.
Both of these show up in a log file (which is hard to visually parse, but useful). Could I suggest a couple things?
1) some kind of heartbeat mechanism where we ping all the BMCs every 5 minutes or something (ipmipower -s)?
2) Check after you issue the ipmipower --on or --off that the system actually turned on or off?