** Description changed: - 1.4.11 lacks any ipv6 support. 1.5.3 (current upstream from 1 Aug 2016) - also lacks ipv6 support. + ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 + from upstream. - Note that both ipmitool (since 2014 or so) and openipmi (since - 2003-11-11) support IPv6. + 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.)
** Description changed: 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. + * If a BMC has only IPv6 addresses, then ipmipower cannot discover it. - * MAAS needs to be able to do just that. + * 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. + * 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.) + * 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.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
