| Summary: | Reboot nfs test does not reliably grab an ip address causing the test to fail | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Gregg Shick <gregg.shick> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Guangze Bai <gbai> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1 | CC: | czhang, dwa, gbai, rlandry, ykun, yshao | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
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.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-11-08 15:42:26 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Gregg Shick
2011-06-29 20:24:26 UTC
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 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 |