MAAS ipmi fails on OCPv3 Roadrunner
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Jason Hobbs | ||
The Open Compute Project |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc.
When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button).
If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui.
Since the commissioning/
Related branches
- Gavin Panella (community): Approve
-
Diff: 456 lines (+329/-44)2 files modifiedetc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect.py (+91/-26)
etc/maas/templates/commissioning-user-data/snippets/tests/test_maas_ipmi_autodetect.py (+238/-18)
affects: | linux → ubuntu |
affects: | ubuntu → linux (Ubuntu) |
no longer affects: | freeipmi (Ubuntu) |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Saucy): | |
importance: | Undecided → Medium |
status: | New → Incomplete |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu Saucy): | |
status: | Incomplete → Confirmed |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in opencompute: | |
status: | New → Triaged |
status: | Triaged → Confirmed |
importance: | Undecided → High |
Changed in maas: | |
assignee: | Andres Rodriguez (andreserl) → Jason Hobbs (jason-hobbs) |
Changed in maas: | |
milestone: | none → 14.04 |
Changed in maas: | |
status: | In Progress → Fix Committed |
tags: | added: server-hwe |
Changed in maas: | |
assignee: | David Duffey (david-duffey) → Jason Hobbs (jason-hobbs) |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in opencompute: | |
status: | Confirmed → Fix Released |
I should add, that using ipmitool manually from a remote host using the 'admin' user I created also works fine. It simply seems that MAAS thinks it has set a user 'maas' when it has not.