Certification Report for patch 3189
- Certifier: Alejandro Álvarez Ayllón
- SA3 Partner: CERN
- Status: Certified
General Background
This patch fixes bugs detected in production (6), preproduction (1) and certification (1) versions, so I had to create three different vNode virtual machines so I could reproduce the bugs and then check if they are really fixed.
All the machines were initialized using
YaimGen 3
.
OS: Scientific Linux 4 32 bits
gLite version: 3.1
Specific Bugs
This bug is more a feature request, added by the patch, so it could not be reproduced. After applying the patch I executed the test suggested by María Alandes, checking if with:
- CONFIG_GRIDMAPDIR=yes the directory /etc/grid-security/gridmapdir/ is created and populated
- CONFIG_GRIDMAPDIR=no the directory /etc/grid-security/gridmapdir/ is not created
when Yaim is executed.
The new feature worked as expected.
Due to this bug when the RPM with the Yaim configuration is created, the wrong path is used. To reproduce the bug, I executed
[root@vtb-generic-97 ~]# /opt/glite/yaim/bin/yaim -p -s /etc/yaim/site-info.def
And checked with "rpm -qpl" the files inside the resulting package, being the path incorrect.
I applied the patch, and executed again
[root@vtb-generic-97 ~]# /opt/glite/yaim/bin/yaim -p -s /etc/yaim/site-info.def
[root@vtb-generic-97 ~]# rpm -qpl yaim-siteinfo-aalvarez-tb-cern-1-1.noarch.rpm
/opt/glite/yaim/examples/siteinfo/mysiteinfo-1
/opt/glite/yaim/examples/siteinfo/mysiteinfo-1/site-info.def
/opt/glite/yaim/examples/siteinfo/mysiteinfo-1/vo.d
/opt/glite/yaim/examples/siteinfo/mysiteinfo-1/vo.d/org.glite.voms-test
After the patch, the path are correct. I also checked that Yaim complains when SITE_NAME and/or SITE_VERSION are not defined, as expected.
Again, the patch adds a new feature, instead of fixing something, so this can not be reproduced.
After applying the patch, I executed the tests suggested by Maria, checking that the user directories were created where they were supposed to be (removing them between tests).
It works, but the directory specified by the user home prefix (wherever it is defined) must exists before running Yaim.
Bug 53271
Fixed certified (Preproduction)
This bug was detected in the
PreProduction version. In this case, I executed Yaim and I checked that I had the wrong output that was reported by Martin Braun:
2009-07-16 11:10:49,206: [INFO] Running Plugins
2009-07-16 11:10:49 lcg-info-dynamic-scheduler: Spec for lrms backend cmd missing in config file
2009-07-16 11:10:49 lcg-info-dynamic-scheduler: Exiting without output, GIP will use static values
2009-07-16 11:10:49,440: [INFO] Reading old LDIF file ...
I had problems reproducing this bug because I was using, by mistake, the production version, instead of the preproduction one, where this bug is located:
bdii-5.0.4-1
glite-yaim-bdii-4.0.4-8
glite-yaim-core-4.0.10-2
glite-yaim-lcg-ce-4.0.6-1
glite-yaim-torque-server-4.0.3-2
glite-yaim-torque-utils-4.0.3-1
PPS-glite-BDII-3.1.21-0
PPS-glite-TORQUE_server-3.1.11-0
PPS-glite-TORQUE_utils-3.1.14-0
PPS-lcg-CE-3.1.34-0
After applying the patch, I tested it again. There were no problems with BDII_top alone and BDII_site alone, but there was one error message when configuring BDII_* with LCG-CE. The source of the error was that I forgot to install the batch system. I installed TORQUE and, after that, everything worked.
Certified by Ricardo Mendes.
Certified by Ricardo Mendes.
In this case, Yaim was ignoring the groups selected in groups.conf, enabling the whole VO instead of only the selected roles.
To reproduce it, I executed the test that Maria suggested, and checked the behaviour. It was as reported.
After applying the patch, I executed again the test and checked if only the required users were created. It worked as it was supposed to.
Bug 54724
Fix certified (Certification)
To reproduce it, I executed Yaim with CONFIG_GRIDMAPDIR="no", and, as reported, the gridmap file was not created. I applied the patch, and executed again Yaim with CONFIG_GRIDMAPDIR set to "yes" first, and "no" later. In both cases the gridmap file was created (I removed it between executions to be sure).