CentOS 5.2 QA

ToDo

A list of things we like to get done for the 5.2 release.

• Update the content of the slides (and translate them)
• Add the updates repo (in the same list as the extra repo)

• Provide a CentOS png to be displayed on the top of the cube (#2633)

• Update the documentation pages (CentOS-5.2 entry for http://www.centos.org/docs/5/)

• the Centos-Media.repo file refers to the Beta key (#2661)

• ...

Bugs

Please submit your bug reports to the CentOS-qa mailing list. It may also be helpful to add them to the list at Bugs, but Karanbir is is currently only watching CentOS-qa for reports.

Tested Hardware lists

Add to the sections below the hardware that you are using to perform the QA tests. Each hardware config is given a letter and that letter is used in the test matrixes below to mark which things you tested.

i386 Hardware

x86_64 Hardware

Test Matrix

This will be used to build more complete matrix. Add things you need/would like to see/... to be tested.

• Check if NFS issues with 5.1 kernels are resolved in 5.2 kernel (#2635)

• Check if IPSec issue with 5.1 kernel 2.6.18-53.1.21 is resolved in 5.2 kernel (#2853)

• Check if the 5.2 kernel has support for the different problematic Realtek gigabit ethernet chipsets. (It looks like it from reading the upstreams release notes)

• Do 32 bit PVM work on a 64 bit dom0. This would crash frequently on 5.1. -- Seems to work with the 5.2 package (TimVerhoeven)

• The way yum handles architectures has apparenlty changed, so please test with upgrades with the old yum and by installing the new yum first and then doing the rest of the upgrade and report back any differences :

(12:48:20 PM) kbsingh: basicaly the way yum handles Arch has changed
(12:48:51 PM) kbsingh: earlier, yum install fo.x86_64 would only consider .x86_64 pkgs for dep resolution
(12:49:07 PM) kbsingh: now it only adds the main package as .x86_64 - but still uses all other ( .* ) for dep resolution
(12:49:20 PM) kbsingh: so you can do yum install foo.x86_64 and bar.x86_64 and bar.i386 installed with it

Stuff the developers need to clear out for 5.2

• ...

Stuff for CentosPlus

• ...

Function Test Matrix

This matrix describes different functional tests. If you successfully tested a item from the matrix then you can add a letter from your hardware profile ( i386 Hardware or x86_64 Hardware ) to the cell (so we know who tested). If you have a failure then add a note below the matrix in the numbered list and add the number of your entry in the cell.

If there are already 3 letters in a cell for that test then you do not need to add a letter if your test was successful. If your test failed then leave the letters in the cell but add the number of your note.

To read testcases click on the testname. If the page for a testcase is empty you are free to add testcases you think are relevant.

Failures Functional tests:

1. ...

Yum priorities testcases

1. General test:
   1. Install yum priorities.
   2. Set the CentOS Base, Updates, and Extras repos to priority 1.
   3. Enable RPMForge.

   4. Try to install subversion and perl-Compress-Zlib. Yum should offer to install these from the CentOS repos.

2. More to come.

Upgrade Test Matrix

TODO

Failures upgrades

1. The yum-utils package is still missing : "Error: Missing Dependency: yum < 3.1.0-0 is needed by package yum-utils" -- Will be build later, it needs anaconda.

2. The anaconda package is still missing : "Error: Missing Dependency: libdhcp6client.so.1 is needed by package anaconda" -- Will be build later.
3. External packages that need libgtkembedmoz.so are broken because of the rebase of xulrunner : "libgtkembedmoz.so is needed by package liferea"
4. External packages that need gtkhtml3 are broken because it has been rebased.

Installation Test Matrix

This matrix describes all the different ways to install CentOS. If you successfully tested a certain way on a certain platform you can add the letter of your hardware profile in the matrix in the correct cell. If you have a failure then add a note below the matrix in the numbered list and add the number of your entry in the cell.

If there are already 5 letters in a cell for tests on real hardware or inside Xen, or if there are already 3 letters for the other platforms then you do not need to add a letter if your test was successful. If your test failed then leave the letters in the cell but add the number of your note.

Todo ...

Rescue Mode

• To be integrated into the installation test matrix.

Serial Console

Serial console works on i386 and x86_64

• ...

Release Notes

Put here things you think should be mentioned in our release notes :

• That for custom kickstart installs the FS should be big enough else anaconda can crash (there a couple of bugs about this in bugs.c.o)
• The gtkhtml3 package has been rebased in 5.2, this means that the ABI for it has changed. We recommend that all software built using gtkhtml3 be recompiled using the new packages; however, CentOS is including a compat-gtkhtml3 package in CentOS-extras for software that can not be recompiled.

• The former installonlyn plugin is now built into yum. You must add the variable installonly_limit = # (where # is the number of kernels you want to maintain installed when a new kernel is installed) to your yum.conf file in CentOS 5.2. The default if nothing is added is 3 kernels. This will need to be updated even if you have the current plugin turned off or set to a different number as it does not happen automatically.

• nss_ldap is broken with bash 3.2 (command substitution) as called out in bz448014. This issue causes substitution errors and prevents su - <any_ldap_user>. If the nscd service is running it will fix the problem, as will the RPM nss_ldap-253-12.el5.centos.<arch>.rpm in our Testing Repository.

• The luci package requires that the package bc is installed, but it is not called out as a require. You may need to manually install bc if you want to run luci. This issue has been filed as the following bugs: bz450854 (upstream) | #2881 (CentOS)

• There is a bug when upgrading bind-chroot where the user's The bind update overwrites any settings like ROOTDIR=/some/other/path with the default ROOTDIR. See this upstream bug for details.

• A kickstart installation that used the repo directive that points to an updates repository would fail the install because the dependency order was totally wrong. (normally glibc and coreutils are one of the first packages because it includes ldconfig and necessary utilities for RPM %pre and %post scripts.

• During an graphical anaconda installation, the mouse pointer that hovers above the Next button on a new screen requires to leave the Next button and re-enter it before you can click it. Usually people have the mouse-pointer on the Next button if the default is fine.