Certification Report for patch 3086
- Certifier: Dennis van Dok
- SA3 Partner: FOM/Nikhef
General Background
The patch includes some minor fixes for glite-yaim-condor-utils. It only contained fixes for issues that concerned packaging,
coding, or configuration changes. None of the standing issues
regarding the actual functioning of Condor as a batch system, which
led to the rejection of previous patch #2593, were addressed.
For the certification of this patch, like earlier patches related to
Condor-as-a-batch-system, I've used a set-up with the following nodes at the Nikhef testbed:
The condormanager node is not a grid node at all. The WN nodes are
plain condor executors, but they have the gLite middleware WN
installation.
Other than installing the stock condor 7.0.4 RPM from
http://www.cs.wisc.edu/condor/
, there were no manual steps required.
I use
CONFIG_USERS=no
as user management is done through LDAP. Where
necessary, I've created local accounts for edguser, glite, tomcat.
General Tests
Only very basic tests were done to ensure the basic functioning of the
system: by doing a globus-jobs-run from a UI it was observed that the
job was indeed submitted correctly to Condor.
Specific Bugs
This bug was found in development; visual inspection of the
YAIM
scripts revealed no trace of the reported problem so I set it to
fixed.
bug 43976
: fix not certified
This bug is a build/integration issue and cannot be reproduced on a local installation.
Inspection of the
ETICS configuration revealed that the bug was not addressed, but
as it doesn't show up in the scripts or the RPM this bug should not be attached to
a patch.
Visual inspection after running
YAIM showed that the suggested changes were implemented.
The fix was observed by visual inspection. Actually the use of 'service' is a Red-Hat specific
idiom and should be replaced by /etc/init.d/.
The fix did not work for me, because the local condor configuration was changed by
YAIM.
I attached a regression test script to the bug.
I checked that the suggested change to blah.config were implemented by this fix.
There were three issues named in this bug; all of them were fixed,
as checked by visual inspection.
--
DennisVanDok - 2009-08-25