MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Jason Hobbs | ||
maas (Ubuntu) |
Fix Released
|
Undecided
|
Jason Hobbs |
Bug Description
Beginning with MAAS 1.5+bzr1977-
I've noticed two scenarios:
1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one.
2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and a pre-generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on).
Workarounds:
In scenario #1 if I go and fill out all of the IPMI information by hand for an affected node, then commissioning, etc. works fine after that.
In scenario #2 if I change the Power User and Power Password parameters in the UI from 'maas' and the pre-generated password to what's already on the BMC (i.e. root/calvin), then commissioning, etc. works fine after that.
This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS.
I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios.
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 27 lines (+7/-2)1 file modifiedetc/maas/templates/power/ipmi.template (+7/-2)
Changed in maas (Ubuntu): | |
assignee: | nobody → Jason Hobbs (jason-hobbs) |
tags: | added: server-hwe |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | none → 14.04 |
Changed in maas (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas (Ubuntu): | |
status: | Fix Committed → Fix Released |
I'm attaching the cloud-init logs from a PowerEdge R805, which exhibits scenario #1.