Latest revision as of 13:50, 1 June 2011

Description

This test case is to run pynfs test suite on a NFSv4 root. The test requires both an NFS server and client. However, the client and server can exist on the same system.

How to test

First, configure the NFS server by creating an NFS mount export

cp /etc/exports /etc/exports.orig
echo '/nfs *(rw,insecure,no_root_squash)' >/etc/exports
mkdir /nfs
service nfs restart

Next, on the client system, download pynfs testsuite from the client.
```
git clone git://linux-nfs.org/~iisaman/pynfs.git 
```
Now, run the pynfs testsuite. Please note, the pynfs test suite will take approximately 30 minutes to run. This makes a good time to grab a cup of your favorite beverage.
```
yum install python-devel krb5-devel gcc
cd pynfs
./setup.py build_ext --inplace
./testserver.py --outfile TESTOUT.log --maketree <server IP>:/nfs all
```
Save the output from the tests to TESTOUT.log, copy /var/log/messages from both the server and client, and then tar and compress them to upload it to the wiki. Please include a link to the uploaded file in your test day results.
```
mkdir log
scp root@<server hostname>:/var/log/messages messages.server
cp TESTOUT.log messages.server /var/log/messages log/
tar czvf /tmp/nfs_pynfs-results-<fedora user name>.tgz log/
```

Expected Results

Step #1 completes without error.
Step #2 completes without error.

The testsuite finishes without unexpected failures. The following known failures and warnings can be ignored.

CID6
LOOK7
SATT1a
CIDCF2
COMP6
CR13
CR14
LINK4a
LINK9
LOOKP2a
OPCF3a
OPEN4
OPEN23b
RD12
RDDR12
RNM11
RNM16
SATT12a
DELEG5
DELEG9
SATT14
SEC7
DELEG11
DELEG12
DELEG13a
DELEG13b
DELEG13c
DELEG13d
DELEG13e
DELEG15
GSS8
CID1
LOCK8c
LOCK18
LOCK21
OPDG9a
OPDG9b
OPDG9c
OPDG9d
OPDG9f
OPDG9s
OPEN16
RD4
RM7
RNM10

Step #4 completes without error.

@@ Line 1: / Line 1: @@
 {{QA/Test_Case
 |description=This test case is to run pynfs test suite on a NFSv4 root.  The test requires both an NFS server and client.  However, the client and server can exist on the same system.
 |actions=
-# First, configure the NFS '''server''' by creating an NFS mount export
+<ol>
-#: <pre>
+<li>First, configure the NFS '''server''' by creating an NFS mount export
-#: cp /etc/exports /etc/exports.orig
+<pre>
-#: echo '/nfs *(rw,insecure,no_root_squash)' >/etc/exports
+cp /etc/exports /etc/exports.orig
-#: mkdir /nfs
+echo '/nfs *(rw,insecure,no_root_squash)' >/etc/exports
-#: service nfs restart</pre>
+mkdir /nfs
-# Next, on the '''client''' system, ''download'' pynfs testsuite from the client.
+service nfs restart</pre>
-#: <pre>
+<li>Next, on the '''client''' system, ''download'' pynfs testsuite from the client.
-#: git clone git://linux-nfs.org/~iisaman/pynfs.git </pre>
+<pre>
-# Now, run the pynfs testsuite.
+git clone git://linux-nfs.org/~iisaman/pynfs.git </pre>
-#: <pre>
+<li>Now, run the pynfs testsuite.  Please note, the ''pynfs'' test suite will take approximately 30 minutes to run.  This makes a good time to grab a cup of your favorite beverage.
-#: cd pynfs
+<pre>
-#: ./setup.py build_ext --inplace
+yum install python-devel krb5-devel gcc
-#: ./testserver.py --maketree <server IP>:/nfs all</pre>
+cd pynfs
+./setup.py build_ext --inplace
+./testserver.py --outfile TESTOUT.log --maketree <server IP>:/nfs all</pre>
+<li>Save the output from the tests to TESTOUT.log, copy {{filename|/var/log/messages}} from both the server and client, and then tar and compress them to [[Special:Upload|upload it]] to the wiki. Please include a link to the uploaded file in your test day results.
+<pre>
+mkdir log
+scp root@<server hostname>:/var/log/messages messages.server
+cp TESTOUT.log messages.server /var/log/messages log/
+tar czvf /tmp/nfs_pynfs-results-<fedora user name>.tgz log/</pre>
+</ol>
 |results=
-# Step #1 completes without error.
+<ol>
-# Step #2 completes without error.
+<li>Step #1 completes without error.
-# The testsuite finishes without unexpected failures.
+<li>Step #2 completes without error.
-#: <pre>
+<li>The testsuite finishes without unexpected failures. The following known failures and warnings can be ignored.
-#: The following known failures can be ignored.
+<pre>
-#: CID6
+CID6
-#: LOOK7
+LOOK7
-#: SATT1a
+SATT1a
-#: CIDCF2
+CIDCF2
-#: COMP6
+COMP6
-#: CR13
+CR13
-#: CR14
+CR14
-#: LINK4a
+LINK4a
-#: LINK9
+LINK9
-#: LOOKP2a
+LOOKP2a
-#: OPCF3a
+OPCF3a
-#: OPEN4
+OPEN4
-#: OPEN23b
+OPEN23b
-#: RD12
+RD12
-#: RDDR12
+RDDR12
-#: RNM11
+RNM11
-#: RNM16
+RNM16
-#: SATT12a
+SATT12a
-#: DELEG5
+DELEG5
-#: DELEG9
+DELEG9
-#: SATT14
+SATT14
-#: SEC7
+SEC7
-#: DELEG11
+DELEG11
-#: DELEG12
+DELEG12
-#: DELEG13a
+DELEG13a
-#: DELEG13b
+DELEG13b
-#: DELEG13c
+DELEG13c
-#: DELEG13d
+DELEG13d
-#: DELEG13e
+DELEG13e
-#: DELEG15
+DELEG15
-#: GSS8
+GSS8
-#: The following known warnings can be ignored.
+CID1
-#: CID1
+LOCK8c
-#: LOCK8c
+LOCK18
-#: LOCK18
+LOCK21
-#: LOCK21
+OPDG9a
-#: OPDG9a
+OPDG9b
-#: OPDG9b
+OPDG9c
-#: OPDG9c
+OPDG9d
-#: OPDG9d
+OPDG9f
-#: OPDG9f
+OPDG9s
-#: OPDG9s
+OPEN16
-#: OPEN16
+RD4
-#: RD4
+RM7
-#: RM7
+RNM10</pre>
-#: RNM10</pre>
+<li>Step #4 completes without error.
+</ol>
 }}
 [[Category:NFS_Test_Cases]]

Search

QA:Testcase nfs pynfs: Difference between revisions

Latest revision as of 13:50, 1 June 2011

Description

How to test

Expected Results