maas enlistment of power8 found ipmi 1.5 should do ipmi 2.0
Bug #1556219 reported by
Scott Moser
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Andres Rodriguez | ||
| 1.9 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
I enlisted a power system in maas.
maas correctly got its ipmi credentials set up, but then would not commission the sytem because it insisted that the power was 'on'.
The ipmi credentials were all correct, but the power type was set to LAN [IPMI 1.5].
Switching it to 2.0 and everything worked fine.
for power arch 2.0 is always going to be right (until ipmi 3.0...)
Related branches
lp:~andreserl/maas/lp1575209_lp1556219
- Andres Rodriguez (community): Approve
- LaMont Jones (community): Approve
- Server Team CI bot (community): Approve
-
Diff: 47 lines (+14/-1)2 files modifiedetc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect.py (+4/-1)
etc/maas/templates/commissioning-user-data/snippets/tests/test_maas_ipmi_autodetect.py (+10/-0)
lp:~andreserl/maas/lp1556219_1.9
- Andres Rodriguez (community): Approve
-
Diff: 60 lines (+16/-1)3 files modifieddocs/changelog.rst (+2/-0)
etc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect.py (+4/-1)
etc/maas/templates/commissioning-user-data/snippets/tests/test_maas_ipmi_autodetect.py (+10/-0)
| Changed in maas: | |
| status: | New → Confirmed |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #1 |
| Changed in maas: | |
| status: | Confirmed → New |
| Changed in maas: | |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| milestone: | none → 2.0.0 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #3 |
| Changed in maas: | |
| assignee: | nobody → Andres Rodriguez (andreserl) |
Revision history for this message
| Scott Moser (smoser) wrote | #4 |
| Changed in maas: | |
| status: | Triaged → Confirmed |
| importance: | Undecided → High |
| Changed in maas: | |
| status: | Confirmed → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This workaround isn't working well for me. I keep having boxes revert to 1.5, then go into Releasing Failed. I've got to manually toggle back to 2.0, release, then attempt redeploy.