Revision as of 10:48, 9 February 2010

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

What to test?

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

Who's available

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

Development - User:steved (EST / UTC-5)
Quality Assurance - User:caiqian (Beijing / UTC+8)

What's needed to test

A system with some kind of network connection
Your hardware profile uploaded to Smolt according to these instructions
An installed Fedora distribution, either:
- Rawhide or a Rawhide live Image available for this test day
- Or an previously installed Fedora 12 system (see Installation guide)

How to test?

Rawhide

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

Install latest rawhide from a local mirror. Please follow this guidance to use rawhide -- Install from a nearby rawhide mirror.
Or, update to rawhide from Fedora 41. For guidance, refer to Releases/Rawhide#Yum_update_from_official_release
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 http://kparal.fedorapeople.org/testdays/2010-02-04_NFSv4/.
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

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

First, be sure you system is fully up to date
```
yum update
```
Next, edit the file /etc/nfsmount.conf and comment out the line that reads
```
Defaultvers=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

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.

Test Results

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	PASS ^[1]	FAIL	PASS	PASS	FAIL ^[2]	↑ RHBZ #561763 ↑ 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	FAIL ^[1]	FAIL	PASS	FAIL ^[2]	FAIL ^[3]	↑ RHBZ #561763 ↑ RHBZ #561763 ↑ RHBZ #562055
User:Rhe	Server HW Client HW	PASS	FAIL	PASS	－	－
User:mcermak	Server HW Client HW	FAIL	FAIL ^[1]	TBD	TBD	TBD	↑ 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	-	-	↑ RHBZ #561763
ykopkova	Server HW Client HW	PASS	FAIL	PASS	TBD	TBD
emcnabb	Server/Client	PASS	FAIL	PASS	FAIL ^[1]	FAIL ^[2]	↑ Test passed, but quite a few call traces in messages file. Haven't looked into if they're related or not. ↑ Hadn't completed after running for 2 - 3 hours, so cancelled
dramsey	Server HW Client HW	PASS	PASS	PASS	FAIL ^[1]	FAIL ^[2]	↑ "kadmin: unable to get default realm" ↑ "kadmin: unable to get default realm"
caiqian	Server HW Client HW	TBD	TBD	TBD	TBD	FAIL ^[1]	↑ RHBZ #562055
mgr	Server/Client HW	PASS	FAIL ^[1]	PASS	PASS	FAIL ^[2]	↑ Do not have permission to upload logs to Fedora wiki, the logs are available here ↑ Hadn't completed after running for 14 hours, so cancelled

[1] RHBZ #561763

[2] Note: the remote server is down. Need to check what is going on there when came back to the office.

[3] RHBZ #561763

[4] RHBZ #561763

[5] RHBZ #562055

[6] NOTE: had to set /nfs *(rw,insecure,no_root_squash,fsid=0) in /etc/exports to make protocol version 4 working

[7] RHBZ #561763

[8] Test passed, but quite a few call traces in messages file. Haven't looked into if they're related or not.

[9] Hadn't completed after running for 2 - 3 hours, so cancelled

[10] "kadmin: unable to get default realm"

[11] "kadmin: unable to get default realm"

[12] RHBZ #562055

[13] Do not have permission to upload logs to Fedora wiki, the logs are available here

[14] Hadn't completed after running for 14 hours, so cancelled

[1]

[2]

[1]

[2]

[3]

[1]

[1]

[1]

[2]

[1]

[2]

[1]

[1]

[2]

@@ Line 163: / Line 163: @@
 | [https://fedoraproject.org/w/uploads/a/a4/Nfs_pynfs-results-dramsey.tgz PASS]
 | [https://fedoraproject.org/w/uploads/6/6f/Nfs_generic-results-dramsey.tgz PASS]
-| <ref>"kadmin: unable to get default realm"</ref> FAIL
+| FAIL <ref>"kadmin: unable to get default realm"</ref>
-| <ref>"kadmin: unable to get default realm"</ref> FAIL
+| FAIL <ref>"kadmin: unable to get default realm"</ref>
 | <references/>
 |-

Search

Test Day:2010-02-04 NFS: Difference between revisions