Certification Report for patches 2834, 3103 and 3214

• Certifier: Alejandro Álvarez Ayllón
• SA3 Partner: CERN

General Background

These three patches allows the info provider to publish information about the version of the meta-packages used to install a service.

• Patch #2834 gLite 3.1, SL4 32 bits. Tested on vtb-generic-109
• Patch #3103 gLite 3.1, SL4 64 bits. Tested on vtb-generic-99
• Patch #3214 gLite 3.2, SL5 64 bits. Tested on vtb-generic-77

General Tests

Patch #2834 Certified

The bug 59381 is fixed by this patch.

Before: glite-version-3.1.0-1.slc4, glite-info-provider-release-1.0.0-5 After: glite-version-3.1.1-2, glite-info-provider-release-1.0.0-9

Rejected once because the initial version of glite-info-provider-release in this patch was 1.0.0-8.

I also tested that the new scripts work correctly:

[root@vtb-generic-109 ~]# glite-version -l
2834
glite-WMS

(The original script only echoed the version of gLite)

The features of the info provider were checked using a diff between the original published data, and the one after the update:

There are some changes in the order, and the new information is published.

Patch #3103 Certified

This patch is for gLite 3.1, SL4 64 bits. It was tested in vtb-generic-88, after destroying and re-deploying the host.

I installed everything from scratch with Yaimgen.

Before: glite-version-3.1.0-1.slc4, glite-info-provider-release-1.0.0-5

I got the output of the LDAP query:

[root@vtb-generic-88 ~]#  ldapsearch -LLL -x -h vtb-generic-88 -p 2170 -b o=grid

After that, I installed the patch

[root@vtb-generic-88 ~]# ./AE_getpatch.sh 3103

glite-version-3.1.1-2.noarch, glite-info-provider-release-1.0.0-9.noarch

The versions of the packages are right, but, just in case, I checked if the bug #53981 was present, and it wasn't. I tested again the new scripts and the information published:

[root@vtb-generic-88 bin]# ./glite-version -l
3103
glite-SE_dpm_mysql

I also checked the diff between the output of the LDAP query before and after.

Patch #3214 Certified

This patch was tested in vtb-generic-77. gLite 3.2, SL5 64 bits.

I installed from scratch the machine using Yaimgen, and checked out the content of the script glite-version

#!/bin/sh
echo 3.2.0

Just to compare the differences with the new version. After that, I installed the patch, but the version of glite-info-provider-release was incorrect: 1.0.0-8.

That version has the bug #53981, and, in addition, the information in the patch about the RPMs name and the ETICS configuration was inconsistent:

glite-info-provider-release-1.0.0-8.noarch.rpm glite-info-provider-release_R_1_0_0_9

So I rejected the patch.

After being reconfigured and rebuilt, I tested it again, and now the versions are the correct ones:

glite-version-3.2.1-1, glite-info-provider-release-1.0.0-9

I reconfigured the node

[root@vtb-generic-77 libexec]# /opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n glite-SE_dpm_mysql

And, again, I compared the information being published, making a diff between the data before, and after the update.

ldapsearch -LLL -x -h vtb-generic-77 -p 2170 -b o=grid

Specific Bugs

Bug #53981 Fixed certified

This bug is fixed by patch #2834. This patch was rejected in the past because it wasn't properly built, so the bug was still present. Now, the version of the package glite-info-provider-release-1.0.0-9.noarch.rpm is the correct.

There have been no test for this bug. Just check in the code if the reported bug (a misplaced space) is still present, or not. And it is not:

Before:

print "dn: GlueServiceDataKey=metapackage-name ,GlueServiceUniqueID=$ID,mds-vo-name=resource,o=grid\n";

Now

print "dn: GlueServiceDataKey=metapackage-name,GlueServiceUniqueID=$ID,mds-vo-name=resource,o=grid\n";

This bug has been checked, just in case, in the other patches, and it is not present.