| | PATCH 3179 |
| |
-
- create a voms-proxy whose lifetime is shorter than 10 minutes
- submit a simple job whose lifetime is shorter than the voms-proxy one and verify its correct termination
|
|
<
< |
- Bug #47804
 : Possible problems configuring blah in CREAM-CE for LSF NOT TESTED
|
>
> |
- Bug #47804: Possible problems configuring blah in CREAM-CE for LSF FIXED
- copy the file profile.lsf from the LSF configuration directory into a new destination, for example /tmp
- define in the site-info.def the variable LSFPROFILE_DIR=/tmp and reconfigure with yaim
- verify that in the file /opt/glite/etc/blah.conf the profile is loaded from the new path
|
| |
- Bug #48786: Load should be one of the parameter of DISABLE_SUBMISSION_POLICY in CREAM FIXED
- specify a low load level in the file /opt/glite/bin/glite_cream_load_monitor
|
| |
- Bug #51993: Proxy renewal not very efficient for multiple jobs having the same delegationid FIXED
- stress the renewal mechanism with a single short delegated proxy, for example with the following test: cream-test-monitored-submit -r 30 -n 2000 -m 2000 -C 50 --sotimeout 60 -j long.jdl -R <ce_id> --vo <vo_name> --valid <00:20>
|
|
<
< |
- Bug #52020: [ yaim-cream-ce ] Support use of file (besides syslog) for glexec logging NOT TESTED
|
>
> |
- Bug #52020: [ yaim-cream-ce ] Support use of file (besides syslog) for glexec logging FIXED
|
| |
- Bug #52050: misleading error message "The problem seems to be related to glexec FIXED
- The CREAM service does not make use of glexec anymore, and therefore this error message can't appear anymore
|
| |
-
- submit a job specifying a simple CE requirements (e.g. cerequirements="other.GlueHostMainMemoryRAMSize > 2000")
- verify that, after the execution of the job, in the tmp directory no files ce-req-file-* are left
|
|
<
< |
- Bug #52577: [ yaim-cream-ce ] create CREAM_GLEXEC_USER_HOME variableNOT TESTED
|
| |
- Bug #52651: CREAM file descriptor overuse FIXED
- try to overload the node with the testsuite: cream-test-monitored-submit -r 30 -n 20000 -m 2000 -C 50 -l log4py.conf -j test.jdl -R --sotimeout 60 --vo dteam --valid 02:00 and verify that with high load the submissions are rejected
- seek "too many open files" in the CREAM log
|
| |
-
- temporary rename the directory /opt/glite/var/cream_sandbox without turning off the service
- submit a job and verify that the failure reports "cannot create the job's working directory!"
|
|
<
< |
- Bug #58941: [yaim-cream-ce] lcmaps confs for glexec and gridftp are not fully synchronized NOT TESTED
|
>
> |
- Bug #58941: [yaim-cream-ce] lcmaps confs for glexec and gridftp are not fully synchronized FIXED
- verify that the file /opt/glite/etc/lcmaps/lcmaps.db is complaint with the one attached to the bug.
|
| |
- Bug #59005: Possible problem with hold/resumed jobs in BUpdaterLSF FIXED
- Verified as reported here
|
| |
- Bug #62436: Possible problem with updater if job remain queued too long FIXED
- Fixed as reported here: 3 jobs lasting 2 hours were submitted to a CREAM CE with only 2 job slots. For the third one the BNotifier logged the right events (i.e. it didn't log status=4 with failurereason=999)
|
|
<
< |
- Bug #62565: yaim-cream-ce requires BLPARSER_HOST even if the new blparser has to be configuredNOT TESTED
|
>
> |
- Bug #62565: yaim-cream-ce requires BLPARSER_HOST even if the new blparser has to be configured FIXED
- Install the CE node from scratch removing the BLPARSER_HOST definition from the site-info.def and defining BLPARSER_WITH_UPDATER_NOTIFIER=true.
- verify that the yaim log about any error concerning the variable above and the BNotifier and the Bupdater run correctly.
|
| |
- Bug #62776: Yaim config for CREAM CE erroneously requires tomcat in glexec group FIXED
- Install the CE node from scratch and verify the following permissions:
|
Copyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.