Red Hat Bugzilla – Bug 365531
TAHI--DHCPv6--The IA option of the recieved DHCPv6 Reply Message includes invalid IA_Address option
Last modified: 2009-01-20 16:38:13 EST
Description of problem:
When having dhcpv6 tests in the server mode,we found that The IA option of
the recieved DHCPv6 Reply Messageincludes invalid IA_Address option in some
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure TAHI test environment.
2. Run the TAHI test suite
3. After the test completes, check for the results
The IA option of the recieved DHCPv6 Reply Message includes invalid
The IA option of the recieved DHCPv6 Reply Message includes no invalid
please refer to
(1) 44 Part C : Reception of Request message if NUT cannt assign any
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fixed upstream, will be in dhcpv6-1.0.5.
the test cases still FAIL On RHEL5.2 with dhcpv6-1.0.10
for more details, pls refer to
In order to debug this problem, we need the test case for RHEL 5.2 with an exact
reproducer, including output with verbose debugging messages from the DHCPV6
software. One way to do this would be to extract the commands that TAHI runs.
The man pages for dhcp6s, dhcp6r, and dhcp6c all show how to generate verbose
Fixed in dhcpv6-1.0.10-2.el5.
*** Bug 436798 has been marked as a duplicate of this bug. ***
Adding email@example.com to the cc list as the manager of the disabled user firstname.lastname@example.org who reported this bug
*** This bug has been marked as a duplicate of 439526 ***
A fix for this bug is in dhcpv6-1.0.10-6.el5 and later builds.
Setting priority to urgent because of EUS.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.