freeipmi lacks IPv6 support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned | ||
freeipmi (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 from upstream.
See also related bug 1645912.
The -h argument to ipmipower needs to be extended to accept [ip:v6::addr]:port type syntax, and the processing of the hostnames needs to take into account ipv6 addresses as well.
[Impact]
* If a BMC has only IPv6 addresses, then ipmipower cannot discover it.
* MAAS needs to be able to do just that.
[Test Case]
* To reproduce / verify the bug, configure a BMC with an IPv6 address, and
try to talk to it.
[Regression Potential]
* If a BMC has both IPv6 and IPv4 addresses in the DNS, and the hostname
is used to control it, then this change will cause ipmipower to try
IPv6 first, where it used to completely ignore IPv6 in the DNS. We
believe this to be the correct behavior and that it does not affect
the current installed base. (IPv6 BMC addresses are not a thing that
we have been able to find anywhere.)
tags: | added: maas-ipv6 |
Changed in maas: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
tags: | removed: needs-upstream-report |
Changed in maas: | |
status: | Confirmed → Triaged |
description: | updated |
description: | updated |
Changed in freeipmi (Ubuntu): | |
status: | Triaged → Fix Released |
Valid bug, but needs to be pushed upstream.