From Fedora Project Wiki
No edit summary |
(fixed <pre> tags) |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case is to run connectathon test suite on a NFSv4 root | |description=This test case is to run connectathon test suite on a NFSv4 root. The test requires both an NFS server and client system. Note, the client and server can exist on the same system. | ||
|actions= | |actions= | ||
<ol> | |||
<li>First step, configure the '''server''' by creating an NFS mount export | |||
<pre> | |||
cp /etc/exports /etc/exports.orig | |||
echo '/nfs *(rw,insecure,no_root_squash)' > /etc/exports | |||
mkdir /nfs | |||
service nfs restart</pre> | |||
</li> | |||
<li> | |||
Next, create test trees on the server | |||
<pre> | |||
git clone git://fedorapeople.org/~steved/cthon04 | |||
cd cthon04 | |||
./runcthon --mkdirs /nfs</pre> | |||
</li> | |||
<li> | |||
Now, on the '''client''', download the connectathon testsuite | |||
<pre> | |||
git clone git://fedorapeople.org/~steved/cthon04</pre> | |||
</li> | |||
<li> | |||
Finally, setup the connectathon testsuite from the client. | |||
<pre> | |||
cd cthon04 | |||
make | |||
mkdir /mnt | |||
chmod 777 /mnt</pre> | |||
</li> | |||
<li> | |||
Run the testsuite from the client by root. | |||
<pre> | |||
./runcthon --server <server IP> --serverdir /nfs --onlyv4 | tee TESTOUT.log</pre> | |||
</li> | |||
<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 together with {{filename|/tmp/nfs*.error}} if any 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 /tmp/nfs*.error log/ | |||
tar czvf /tmp/nfs_connectathon-results-<fedora user name>.tgz log/</pre> | |||
</li> | |||
</ol> | |||
|results= | |results= | ||
# Step #1 completes without error. | # Step #1 completes without error. | ||
# Step #2 completes without error. | |||
# Step #3 completes without error. | |||
# Step #4 completes without error. | |||
# The testsuite finishes without error; no nfs*.error files in /tmp. | # The testsuite finishes without error; no nfs*.error files in /tmp. | ||
# Step #6 completes without error. | |||
}} | }} | ||
[[Category:NFS_Test_Cases]] | [[Category:NFS_Test_Cases]] |
Latest revision as of 17:26, 1 June 2011
Description
This test case is to run connectathon test suite on a NFSv4 root. The test requires both an NFS server and client system. Note, the client and server can exist on the same system.
How to test
- First step, configure the 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, create test trees on the server
git clone git://fedorapeople.org/~steved/cthon04 cd cthon04 ./runcthon --mkdirs /nfs
-
Now, on the client, download the connectathon testsuite
git clone git://fedorapeople.org/~steved/cthon04
-
Finally, setup the connectathon testsuite from the client.
cd cthon04 make mkdir /mnt chmod 777 /mnt
-
Run the testsuite from the client by root.
./runcthon --server <server IP> --serverdir /nfs --onlyv4 | tee TESTOUT.log
-
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 together with/tmp/nfs*.error
if any 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 /tmp/nfs*.error log/ tar czvf /tmp/nfs_connectathon-results-<fedora user name>.tgz log/
Expected Results
- Step #1 completes without error.
- Step #2 completes without error.
- Step #3 completes without error.
- Step #4 completes without error.
- The testsuite finishes without error; no nfs*.error files in /tmp.
- Step #6 completes without error.