Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I find elapsed time for all retransmission release message are zero. http://focus.bne.redhat.com/~ryang/ipv6ready/DHCPv6_Self_Test_P2_1_1_0_client_latest/rfc3315/59.html Version-Release number of selected component (if applicable): dhclient-4.1.1-13.fc12 How reproducible: always Steps to Reproduce: 1.start a server and a client 2.after client got address stop server 3.release client address Actual results: all release message have zero elapsed time Expected results: elapsed time option is not empty Additional info:
Can you try this build ? http://koji.fedoraproject.org/koji/buildinfo?buildID=167786
Verified in this build (dhcp-4.1.1-14.fc12)
dhcp-4.1.1-17.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/dhcp-4.1.1-17.fc13
dhcp-4.1.1-15.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/dhcp-4.1.1-15.fc12
dhcp-4.1.1-15.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dhcp'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dhcp-4.1.1-15.fc12
verified in dhcp-4.1.1-15.fc12
dhcp-4.1.1-16.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dhcp'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dhcp-4.1.1-16.fc12
Hi Jiri The elapsed time of first confirm msg is not null in dhcp-4.1.1-16.fc12. This is a regression. dhcp-4.1.1-15.fc12 has not this problem. Pls have a check. After whole dhcp-4.1.1-16.fc12 run finished I'll re-test it to confirm the regression. Thanks,
Verified. Elapsed Time of release message is ok now. I'll verified this bug and reopen bug #574677
(In reply to comment #8) > The elapsed time of first confirm msg is not null in dhcp-4.1.1-16.fc12. > This is a regression. dhcp-4.1.1-15.fc12 has not this problem. Pls have a > check. After whole dhcp-4.1.1-16.fc12 run finished I'll re-test it to confirm > the regression. Hi Yang, I was not touching the code between dhcp-4.1.1-15.fc12 and dhcp-4.1.1-16.fc12. The only change there was that I moved one script (/etc/NetworkManager/dispatcher.d/10-dhclient) from dhcp package to dhclient subpackage. So I guess the problem is somewhere in the test.
(In reply to comment #10) > (In reply to comment #8) > > The elapsed time of first confirm msg is not null in dhcp-4.1.1-16.fc12. > > This is a regression. dhcp-4.1.1-15.fc12 has not this problem. Pls have a > > check. After whole dhcp-4.1.1-16.fc12 run finished I'll re-test it to confirm > > the regression. > Hi Yang, > I was not touching the code between dhcp-4.1.1-15.fc12 and dhcp-4.1.1-16.fc12. > The only change there was that I moved one script > (/etc/NetworkManager/dispatcher.d/10-dhclient) from dhcp package to dhclient > subpackage. > So I guess the problem is somewhere in the test. Got it. I'll test again after finish the whole test once.
dhcp-4.1.1-16.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
dhcp-4.1.1-21.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.