Errors to query/control power are not propagated to the UI

Bug #2042433 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned
3.5
Triaged
High
Unassigned

Bug Description

Currently, power checking and control for IPMI are broken (bug 2042429). Yet the machine listing doesn't show any power related errors at all.

There are also no mention of any failures in the event log.

Revision history for this message
Björn Tillenius (bjornt) wrote :

There's one power error in the listing, but it's from 2 weeks ago.

description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote :
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 3.5.0
Changed in maas:
assignee: nobody → Anton Troyanov (troyanov)
Changed in maas:
milestone: 3.5.0 → 3.6.0
Changed in maas:
assignee: Anton Troyanov (troyanov) → nobody
Jacopo Rota (r00ta)
Changed in maas:
assignee: nobody → Jacopo Rota (r00ta)
Revision history for this message
Jacopo Rota (r00ta) wrote :

Comparison between 3.4 and 3.5:

- 3.4:
  - we fail the power action after ~4 minutes
  - we transition the machine to `Failed XXX` depending on the original action
  - we mark the tests as Failed

- 3.5:
  - we log the first error after ~2 minutes and we keep trying for ~10 minutes. After that we log `Aborting COMMISSIONING and reverting to NEW. Unable to power control the node. Please check power credentials.`
  - we transition the machine back to its original status
  - we mark the tests as Aborted

The behaviour of 3.5 looks reasonable to me. I'm marking this bug as invalid but feel free to reopen if you think 3.5 should do something different.

Changed in maas:
status: Triaged → Invalid
Revision history for this message
Jacopo Rota (r00ta) wrote :
Revision history for this message
Jacopo Rota (r00ta) wrote :
Revision history for this message
Jacopo Rota (r00ta) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :

I still feel that this is something that we need to address, but we don't have to address it for 3.5.0.

Already, 4 minutes is quite a long time for any feedback (assuming that you don't actively look at the event log), and increasing that to 10 minutes is going in the wrong direction.

Changed in maas:
status: Invalid → Triaged
assignee: Jacopo Rota (r00ta) → nobody
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.