Red Hat Bugzilla – Bug 365661
TAHI--DHCPv6--The returned status code of the recieved DHCPv6 Advertise Message is not NoAddrsAvail
Last modified: 2009-01-20 16:38:18 EST
Description of problem:
When having dhcpv6 tests about "Advertise message transmission with Status
Code Option, NoAddrAvail" in the server mode,we found that the returned status
code of the recieved DHCPv6 Advertise Message is not NoAddrsAvail.
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 returned status code of the recieved DHCPv6 Advertise Message is not
The returned status code of the recieved DHCPv6 Advertise Message should be
please refer to
(1) 29 Part D : Advertise message transmission with Status Code Option,
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
also about status code,
please refer to
(1) 59 Part C : Reception of Release message with invalid IA_NA Identifier
(2) 62 Part C : Reception of Decline message with invalid IA_NA Identifier
Fixed upstream and will be in dhcpv6-1.0.5.
*** Bug 365611 has been marked as a duplicate of this bug. ***
but the test cases FAIL on RHEL5.2 with dhcpv6-1.0.10
for more details, pls refer to
This works when there is only one IA_NA but fails for multiple IA_NA options.
Known issue, OK for DoD cert.
Adding firstname.lastname@example.org to the cc list as the manager of the disabled user email@example.com who reported this bug
*** This bug has been marked as a duplicate of 439526 ***
A fix for this issue should be in dhcpv6-1.0.10-6.el5 and later builds.
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.