[2.0] Digital Loggers PDU are not cycled before commissioning/deployment

Bug #1598116 reported by ptylenda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

Steps to reproduce:
1. Add a new machine to MAAS
2. Wait for "New" status
3. Assign power management settings to use Digital Loggers, Inc. PDU (or probably some others than IPMI?)
4. Commission
5. Deploy when commissioning is finished

Result:
Deployment will fail, because of:
Queried node's BMC - Power state queried: on Fri, 01 Jul. 2016 12:51:32
Node changed status - From 'Deploying' to 'Failed deployment' Fri, 01 Jul. 2016 12:51:12
Powering node on Fri, 01 Jul. 2016 12:10:09
User starting deployment - (root) Fri, 01 Jul. 2016 12:10:08
User acquiring node - (root) Fri, 01 Jul. 2016 12:10:08

In other words, the machine is left in power state "on" after enlisting/commissioning, so without manually powering the machine off in web power switch commissioning/deployment (respectively) will fail as no actions will be performed.

There should be an option (probably default?) to power cycle such machines, so that they are powered off and powered on later. I don't know how it looks for different power switches, but in case of Digital Loggers there is also a possibility to trigger power cycle from web interface which will use predefined on-off delay.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

MAAS support for PDU's is not the same support for machines. MAAS does not power cycle machines when they are on and you try to do what you are trying to do, because usually, the machine will be turned off. We'll consider this in our next iteration.

Changed in maas:
importance: Undecided → Wishlist
status: New → Triaged
milestone: none → 2.1.0
Changed in maas:
milestone: 2.0.1 → 2.1.0
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Changed in maas:
milestone: 2.1.3 → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.x
Changed in maas:
milestone: 2.2.x → 2.3.0rc2
Changed in maas:
milestone: 2.3.0rc2 → 2.3.x
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
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.