Certification Report for patch 3438 and 3439
- Certifier: Alejandro Álvarez Ayllón
- SA3 Partner: CERN
- Status: Certified
General Background
These two patches fix some bugs in the Yaim module for CREAM.
- Patch #3438
, for gLite 3.1 (32 bits), tested on vtb-generic-45.cern.ch
- Patch #3439
, for gLite 3.2 (64 bits), tested on vtb-generic-49.cern.ch
For gLite 3.2 glite-CREAM is introduced by
patch #3260
; and glite-TORQUE_server and glite-TORQUE_utils are in preproduction (by the time of certification)
The updated package (glite-yaim-cream-ce-4.0.9-3.noarch.rpm) is the same for both patches, as it is not related to a specific architecture. Therefore, except bug 57141, these bug are shared between both patches.
Specific Bugs
I asked Maria Alandes to check this in
ETICS, and she said that this is OK.
I obtained the LDAP published information before and after applying the patch, and observing this fragment:
< GlueCECapability: unset
---
> GlueCECapability: CPUScalingFactorSI00=100
> GlueCECapability: Share=dteam:90
< GlueHostProcessorOtherDescription: unset
---
> GlueHostProcessorOtherDescription: Cores=4
we can see that the bug is fixed.
NOTE: CPUScalingFactorSI00 is supposed to be
CPUScalingReferenceSI00, but the mistake is in the site-info.def configuration file. The patch is doing what it is supposed to do.
Bug #57141
(Only for 3438) Fix certified
I checked the content of the script /opt/glite/yaim/functions/config_cream_glexec
The suggested change, to fix the problem in 64 bits machines, is in the code
yaimlog DEBUG "OS_ARCH = ${OS_ARCH}"
moddir=${GLITE_LOCATION}/lib64/modules
if [ ! -d $moddir ]; then
# 32-bit installation
moddir=${GLITE_LOCATION}/lib/modules
fi
Again, to check this bug is fixed, I just checked out the code in the script /opt/glite/yaim/functions/config_cream_gip.
For VOView:
GlueCEInfoApplicationDir: `get_vo_param ${VO} SW_DIR`
For the CEs:
GlueCEInfoApplicationDir: ${VO_SW_DIR}
That's the expected behaviour.