Bug 134368

Summary:	Nfsv4 : Pynfs tests failing - LOCK with newlockowner's lockseqid=1 should return NFS4ERR_BAD_SEQID, instead got NFS4_OK
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Forgotten User b5BnQSUi71 <forgotten_b5BnQSUi71>
Component:	Other	Assignee:	Olaf Kirch <okir>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Alpha 2
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User b5BnQSUi71 2005-11-18 10:08:27 UTC

Pynfs (now called newpynfs), a suite of several Python tools for NFS4 is used for testing NFSv4 RFC compliance. It can be downloaded here http://www.citi.umich.edu/projects/nfsv4/pynfs/

Steps to reproduce the bug:
1. Setup NFSv4 server in SUSE 10.1 Alpha 2
2. Install newpynfs
3. Run the pynfs testserver.py script
./testserver.py --maketree <hostname> all -v
        or
python testserver.py --maketree <hostname> all -v
4. The results will be store in out_last file
5. Redirect results to a text file
./showresults.py out_last > SUSE10.1.txt
6. The following test is failing 
LOCK8c   st_lock.testNonzeroLockSeqid                     : FAILURE
    LOCK with newlockowner's lockseqid=1 should return
    NFS4ERR_BAD_SEQID, instead got NFS4_OK

Comment 2 Forgotten User b5BnQSUi71 2005-11-23 11:16:33 UTC


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