From Fedora Project Wiki

2010-02-04 All day #fedora-test-day (webirc)

What to test?[edit]

Today's installment of Fedora Test Day will focus on NFS with a focus on NFSv4 default.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

What's needed to test[edit]

How to test?[edit]


To test using Rawhide, you may prepare your system using one of the following methods.

  1. Install latest rawhide from a local mirror. Please follow this guidance to use rawhide -- Install from a nearby rawhide mirror.
  2. Or, update to rawhide from Fedora 40. For guidance, refer to Releases/Rawhide#Yum_update_from_official_release
  3. Alternatively, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found at
  4. Either way, be sure you are running with at least kernel-2.6.33-0.24.rc5.git1.fc13, linux-firmware-20100106-1.fc13 and nfs-utils-1.2.1-16.fc13

Fedora 12[edit]

Testing can be also be performed on Fedora 12 system with only a few changes.

  1. First, be sure you system is fully up to date
    yum update
  2. Next, edit the file /etc/nfsmount.conf and comment out the line that reads
  3. Finally, be sure you are using at least nfs-utils-1.2.1-5.fc12 (koji, bodhi)
    yum --enablerepo=updates-testing update nfs-utils

Test Cases[edit]

Basically, NFS can be tested with both server and client on the same machine, and with different bare-metal or virtual systems. Testers will need to setup a NFS server, and run automated NFS testsuites from client systems. In addition, we will use generic filesystem testsuites to exercise NFS filesystem integrity. An important part of the test event is to make sure everything is working properly after we have switched to NFSv4 by default in Fedora 13.

Also, we will test Secure NFS. All the results will be reported to the table below.

  1. QA:Testcase_nfs_connectathon
  2. QA:Testcase_nfs_pynfs
  3. QA:Testcase_nfs_generic
  4. QA:Testcase_nfs_connectathon_secure
  5. QA:Testcase_nfs_generic_secure

Test Results[edit]

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example:

User Smolt Profile connectathon pynfs generic-fs connectathon secure generic-fs secure References
caiqian Server HW

Client HW



  1. RHBZ #561763
  2. Note: the remote server is down. Need to check what is going on there when came back to the office.
User:mvadkert Server HW

Client HW







  1. RHBZ #561763
  2. RHBZ #561763
  3. RHBZ #562055
User:Rhe Server HW

Client HW

User:mcermak Server HW

Client HW



  1. NOTE: had to set /nfs *(rw,insecure,no_root_squash,fsid=0) in /etc/exports to make protocol version 4 working
User:kparal Server+Client HW PASS - - - -
User:mgahagan Server HW Client HW - - TBD TBD TBD
jlaska Server+Client HW FAIL [1] PASS PASS - -
  1. RHBZ #561763
ykopkova Server HW Client HW PASS FAIL PASS FAIL [1] FAIL [2]
  1. "Possible RHBZ #562055"
  2. "Possible RHBZ #562055 and SELinux messages"
emcnabb Server/Client PASS FAIL PASS FAIL [1] FAIL [2]
  1. Test passed, but quite a few call traces in messages file. Haven't looked into if they're related or not.
  2. Hadn't completed after running for 2 - 3 hours, so cancelled
dramsey Server HW Client HW PASS PASS PASS FAIL [1] FAIL [2]
  1. "kadmin: unable to get default realm"
  2. "kadmin: unable to get default realm"
caiqian Server HW

Client HW

  1. RHBZ #562055
mgr Server/Client HW PASS FAIL [1] PASS PASS FAIL [2]
  1. Do not have permission to upload logs to Fedora wiki, the logs are available here
  2. Hadn't completed after running for 14 hours, so cancelled