Description of problem: Reboot nfs fails to grab an IP address from dhcp much more than it succeeds. Version-Release number of selected component (if applicable): RH 6.1 GA / v7-1-3-46 How reproducible: 75+% of the attempts Steps to Reproduce: 1.Install RH6.1 x64 2.Install v71-3-46 testkit and supporting rpms 3.Execute v7 reboot nfs test. Actual results: When it kicks out to the console screen where it should grab an IP and write the dump file to the remote test server, dhcp fails to acquire an address and the test fails. below is approximately the error message seen: Mapping eth0 to eth0 Sending discovery (tries 4 times) Unable to get DHCP address Eth0 failed to come up. Expected results: DHCP should work. Additional info: This is being tested on a DL385 G7. All nics connected, all dhcp. I see no dhcp lease issues outside of the kdump request. I attempted to set static on the nic, but it still tries using dhcp.
I have added the link_delay=60 option to kdump.conf. With this option, it appears to be grabbing an IP much more reliably.
Created attachment 510707 [details] sosreport
We have retested this on a different system (360 G7, same broadcom 5709)on a separate and completely isolated network. Seeing the same failure to grab an IP. link_delay 60 fixes the problem in this case as well.
Created attachment 514004 [details] kdump test patch setting link_delay to 60 sec if not present if link_delay is already set, the kdump test will not change the setting.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In v7 1.3, reboot nfs test might fail to grab an IP address when kexec kernel is trying to dump vmcore to an NFS server due to link_delay value not set in kdump.conf. This issue has been fixed in v7 1.4, now kdump (originally reboot) test will set link_delay value to 60s to make sure kexec kernel can wait for enough time to obtain an IP address before dumping vmcore to NFS server. Note that if user has ever set link_delay value in kdump.conf, kdump test won't override it. So please make sure the value of link_delay is correct before running the test.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1436.html