Bug 1296674
Summary: | rhel6-nfs.rhts.eng.bos.redhat.com/nfsvers=3_udp/special hangs mustang | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Bill Peck <bpeck> |
Component: | kernel-aarch64 | Assignee: | nfs-maint |
kernel-aarch64 sub component: | NFS | QA Contact: | Filesystem QE <fs-qe> |
Status: | CLOSED NOTABUG | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | steved |
Version: | 7.3 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-13 15:16:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Peck
2016-01-07 19:48:13 UTC
failing jobs: https://beaker.engineering.redhat.com/jobs/1185089 https://beaker.engineering.redhat.com/recipes/2401654 link to console logs: http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2016/01/11848/1184858/2401654/console.log http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2016/01/11850/1185089/2402238/console.log (In reply to Bill Peck from comment #1) > failing jobs: > https://beaker.engineering.redhat.com/jobs/1185089 > https://beaker.engineering.redhat.com/recipes/2401654 It appears these failures happen because the watchdog timer timed out. > > link to console logs: > http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2016/01/11848/ > 1184858/2401654/console.log > http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2016/01/11850/ > 1185089/2402238/console.log These log show that there was newtwork problems is the RHEL6 NFS server. It is a well known fact that using UDP on a noisy network is not a good thing. That's why TCP is the default since its handles those types of networks much better Assuming this is not constantly reproducible, I'm going to close this as notabug since this is a know issue with the UDP transport. Hi Steve, The system attempted to reboot first (thats the localwatchdog) but was unable to and that's why the external watchdog kicked in. Even with using udp shouldn't the system be able to reboot? yes... unless there is some type of hanging mount |