From Fedora Project Wiki

Revision as of 14:58, 30 April 2009 by Jlaska (talk | contribs) (Updated table header)

DATE TIME WHERE
Thu April 30, 2009 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-qa)

What to test?

Today's installment of Fedora Test Day will focus on:

If you come to this page after the test day, your testing of SSSD is still valuable, and you can use the information on this page to test SSSD in your setup and provide feedback. The provided LDAP server may no longer be available, so the steps to test against a private LDAP server should be followed in this case.

Who's available

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

Prerequisites for Test Day

FIXME - subject to change when the LiveCD appears.

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture MD5SUM
i386 022137eeb466410221a3339519a867c7
x86_64 68db3894c1d47dba2ae73330fbd5e409

Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using

yum --enablerepo=rawhide update syslinux

How to test?

Before proceeding to the test cases themselves, you need to install and configure sssd. The necessary steps are outlined on the Installation page. If you are using the Test Day live image, the installation steps will be completed for you.

When done, please follow each of these test cases:

NSS (User identity)

PAM (User authentication)

Report your Results

If you have problems with any of the tests, report a bug to Trac. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from Stephen Gallagher as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, as a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the private LDAP test as you do not have access to an LDAP server), enter the word N/A. In the comments column, you can enter any short, additional information about your testing environment.

NSS Tests

User Native Local Legacy Local Remote LDAP Remote Private LDAP Comments
Stephen Gallagher PASS PASS PASS PASS Tests performed on x86_64 LiveCD
Michal Nowak PASS PASS PASS N/A HW
Zbysek MRAZ PASS PASS PASS -
Robert M Williams PASS PASS PASS - LiveCD in VM

PAM Tests

User Native Local Legacy Local Native LDAP Legacy LDAP Native Private LDAP Legacy Private LDAP Comments
Stephen Gallagher PASS FAIL (LiveCD removed pam_cracklib.so from system-auth. Once re-added, PASS) FAIL PASS FAIL PASS Tests performed on x86_64 LiveCD
Michal Nowak PASS FAIL FAIL FAIL N/A N/A HW