IPMI detection ends up with power_address of 0.0.0.0
Bug #1064224 reported by
Julian Edwards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Andres Rodriguez | ||
1.2 |
Fix Released
|
Critical
|
Andres Rodriguez | ||
maas (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Quantal |
Fix Released
|
Critical
|
Unassigned | ||
Raring |
Fix Released
|
Critical
|
Unassigned |
Bug Description
After commissioning my node, I see the power user and password set OK, but the power address is 0.0.0.0.
The BMC happens to have failed to DHCPed an address yet (I don't know why); whether that has any bearing on this I don't know but at the very least we should not set an ip address of 0.0.0.0.
Related branches
lp:~andreserl/maas/maas_ipmi_lp1064224
- Julian Edwards (community): Approve
-
Diff: 69 lines (+23/-5)2 files modifiedcontrib/preseeds_v2/enlist_userdata (+12/-3)
etc/maas/commissioning-user-data (+11/-2)
lp:~andreserl/maas/maas.quantal_ipmi_lp1064224
- Julian Edwards (community): Approve
-
Diff: 69 lines (+23/-5)2 files modifiedcontrib/preseeds_v2/enlist_userdata (+12/-3)
etc/maas/commissioning-user-data (+11/-2)
lp:~andreserl/maas/quantal_update_changelog
- Andres Rodriguez (community): Approve
-
Diff: 31 lines (+23/-1)1 file modifieddebian/changelog (+23/-1)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas: | |
status: | Triaged → Incomplete |
Changed in maas: | |
milestone: | none → 12.10 |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
status: | Incomplete → Triaged |
Changed in maas: | |
milestone: | 12.10 → 12.10-stabilization |
Changed in maas: | |
milestone: | 12.10-stabilization → none |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas (Ubuntu Quantal): | |
status: | New → Triaged |
Changed in maas (Ubuntu Raring): | |
status: | New → Triaged |
Changed in maas (Ubuntu Quantal): | |
importance: | Undecided → Critical |
Changed in maas (Ubuntu Raring): | |
importance: | Undecided → Critical |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is related to but not the same as bug 1061577, where on highbank we always set the IP to 0.0.0.0 since it never reports a correct IP address. At the moment, bug 1061577 has a simple workaround which is just to change the IP from 0.0.0.0 to the correct one in the Web UI. However this is fixed, please try and keep some workaround possible for bug 1061577.