Bug 461008 - RHTS connectathon failures in readdir (test6)
Summary: RHTS connectathon failures in readdir (test6)
Keywords:
Status: CLOSED DUPLICATE of bug 430946
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jeff Layton
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-03 13:12 UTC by Vivek Goyal
Modified: 2009-06-09 11:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-09 11:55:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vivek Goyal 2008-09-03 13:12:53 UTC
Description of problem:

I have noticed rhts connectathon readdir (test6) failure twice. Once on i386 and other time
on x86_64.

http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=4093065
http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=3956545

Version-Release number of selected component (if applicable):

Noticed on 78.5.EL and 78.7.EL

How reproducible:

Noticed it twice so far.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Tests failed.

Expected results:

Test should pass
Additional info:

Comment 1 Jeff Layton 2008-11-18 02:44:19 UTC
The 3956545 logs are still there. They show this:

device eth0 entered promiscuous mode
SELinux: initialized (dev 0:13, type nfs), uses genfs_contexts
NFS: readdir reply truncated!
device eth0 left promiscuous mode

...and the capture shows a readdir reply transmission that's truncated. This basically a server side problem and is probably a duplicate of bug 430946, though bug 443655 should cause the client to actually return an error when it receives a reply like this.

The server looks like it's RHEL4, and I think a more recent kernel was installed on Oct 13:

-rw-r--r--  1 root root 1317582 Oct 13 09:06 initrd-2.6.9-78.ELsmp.img

...are you still seeing this? Do you happen to know what kernel was running on the server at the time that you saw this?

Comment 2 Jeff Layton 2009-06-09 11:55:18 UTC
No word in several months. I'm going to go ahead and close this as a duplicate of bug 430946. Please reopen if this is still being seen with the server running recent kernels.

*** This bug has been marked as a duplicate of bug 430946 ***


Note You need to log in before you can comment on or make changes to this bug.