| 2016-08-30 16:43:35 |
LaMont Jones |
bug |
|
|
added bug |
| 2016-09-01 17:12:13 |
Joshua Powers |
freeipmi (Ubuntu): status |
New |
Triaged |
|
| 2016-09-01 17:12:15 |
Joshua Powers |
freeipmi (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2016-09-01 17:12:25 |
Joshua Powers |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2016-09-01 17:12:53 |
Joshua Powers |
tags |
|
needs-upstream-report |
|
| 2016-09-08 14:31:54 |
Andres Rodriguez |
tags |
needs-upstream-report |
maas-ipv6 needs-upstream-report |
|
| 2016-09-08 14:34:33 |
Andres Rodriguez |
bug task added |
|
maas |
|
| 2016-09-08 14:34:40 |
Andres Rodriguez |
maas: status |
New |
Confirmed |
|
| 2016-09-08 14:34:45 |
Andres Rodriguez |
maas: importance |
Undecided |
Critical |
|
| 2016-09-09 15:50:28 |
LaMont Jones |
bug watch added |
|
https://github.com/chu11/freeipmi-mirror/issues/6 |
|
| 2016-09-09 16:11:26 |
LaMont Jones |
tags |
maas-ipv6 needs-upstream-report |
maas-ipv6 |
|
| 2016-09-26 13:55:12 |
Gavin Panella |
maas: status |
Confirmed |
Triaged |
|
| 2016-11-23 18:20:21 |
LaMont Jones |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-11-23 18:20:21 |
LaMont Jones |
bug task added |
|
freeipmi (Ubuntu Xenial) |
|
| 2016-11-28 17:20:55 |
LaMont Jones |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-11-28 17:20:55 |
LaMont Jones |
bug task added |
|
freeipmi (Ubuntu Yakkety) |
|
| 2016-11-29 23:46:33 |
LaMont Jones |
description |
1.4.11 lacks any ipv6 support. 1.5.3 (current upstream from 1 Aug 2016) also lacks ipv6 support.
Note that both ipmitool (since 2014 or so) and openipmi (since 2003-11-11) support IPv6. |
ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 from upstream.
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.) |
|
| 2016-11-29 23:47:04 |
LaMont Jones |
description |
ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 from upstream.
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.) |
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.) |
|
| 2016-11-30 00:00:29 |
Chris Halse Rogers |
freeipmi (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2016-11-30 00:00:33 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-30 00:00:39 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2016-11-30 00:00:44 |
Chris Halse Rogers |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2016-11-30 00:01:38 |
Chris Halse Rogers |
freeipmi (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-11-30 16:26:32 |
LaMont Jones |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2016-12-07 13:44:42 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-12-07 13:44:55 |
Launchpad Janitor |
freeipmi (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-12-07 13:45:21 |
Launchpad Janitor |
freeipmi (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-17 00:37:48 |
Nish Aravamudan |
freeipmi (Ubuntu): status |
Triaged |
Fix Released |
|
| 2017-01-04 17:24:00 |
LaMont Jones |
maas: status |
Triaged |
Fix Released |
|
