Regression Test Work Plan
Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented
STATUS:
Implemented
To test the fix:
- disable the submission on the CE
This can be achieved via the
`glite-ce-disable-submission host:port`
command (provided by the CREAM CLI package installed on the UI), that can be issued only by a CREAM CE administrator, that is the DN of this person must be listed in the
/etc/grid-security/admin-list
file of the CE.
Output should be: "Operation for disabling new submissions succeeded"
- restart tomcat on the CREAM CE (service tomcat restart - on CE)
- verify if the submission is disabled (glite-ce-allowed-submission)
This can be achieved via the `
glite-ce-enable-submission host:port`
command (provided by the CREAM CLI package installed on the UI).
Output should be: "Job submission to this CREAM CE is enabled"
Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment. - Implemented
STATUS:
Implemented
To test the fix, simply run on the CREAM CE as root the
JobDBAdminPurger.sh. E.g.:
# JobDBAdminPurger.sh -c /etc/glite-ce-cream/cream-config.xml -u <user> -p <passwd> -s DONE-FAILED,0
START jobAdminPurger
It should work without reporting error messages:
-----------------------------------------------------------
Job CREAM595579358 is going to be purged ...
- Job deleted. JobId = CREAM595579358
CREAM595579358 has been purged!
-----------------------------------------------------------
STOP jobAdminPurger
Bug #81824 yaim-cream-ce should manage the attribute bupdater_loop_interval. - Implemented
STATUS:
Implemented
To test the fix, check in the CREAM CE if the file /etc/blah.config contains the parameter bupdater_loop_interval.
Bug #83238 Sometimes CREAM does not update the state of a failed job. - Implemented
STATUS:
Implemented
To test the fix, try to kill by hand a job.
The status of the job should eventually be:
Status = [DONE-FAILED]
ExitCode = [N/A]
FailureReason = [Job has been terminated (got SIGTERM)]
Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Not implemented
STATUS:
Not implemented
To test the fix, submit some jobs and then reconfigure the service with a different value of
CREAM_SANDBOX_PATH
. Then try, with the
JobDBAdminPurger.sh
script, to purge some jobs submitted before the switch.
It must be verified:
- that the jobs have been purged from the CREAM DB (i.e. a
glite-ce-job-status
should not find them anymore)
- that the relevant CREAM sandbox directories have been deleted
STATUS:
Not implemented
To test the fix, query the resource bdii of the CREAM-CE:
ldapsearch -h <CREAM CE host> -x -p 2170 -b "o=grid" | grep -i foreignkey | grep -i glueceuniqueid
Entries such as:
GlueForeignKey: GlueCEUniqueID=cream-35.pd.infn.it:8443/cream-lsf-creamtest1
i.e.:
GlueForeignKey: GlueCEUniqueID=<CREAM CE ID>
should appear.
Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Not implemented
STATUS:
Not implemented
To test the fix, issue the following ldapsearch query towards the resource bdii of the CREAM-CE:
$ ldapsearch -h cream-35 -x -p 2170 -b "o=grid" | grep -i GlueCEStateWaitingJobs | grep -i 444444
It should not find anything
Bug #87361 The attribute cream_concurrency_level should be configurable via yaim. - Implemented
STATUS:
Implemented
To test the fix, set in
seiteinfo.def
the variable
CREAM_CONCURRENCY_LEVEL
to a certain number (n). After configuration verify that in
/etc/glite-ce-cream/cream-config.xml
there is:
cream_concurrency_level="n"
Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Not implemented
STATUS:
Not implemented
To test the fix, submit the following JDL using
glite-ce-job-submit
:
Environment = {
"GANGA_LCG_VO='camont:/camont/Role=lcgadmin'",
"LFC_HOST='lfc0448.gridpp.rl.ac.uk'",
"GANGA_LOG_HANDLER='WMS'"
};
executable="/bin/env";
stdoutput="out.out";
outputsandbox={"out.out"};
outputsandboxbasedesturi="gsiftp://localhost";
When the job is done, retrieve the output and check that in
out.out
the variables
GANGA_LCG_VO
,
LFC_HOST
and
GANGA_LOG_HANDLER
have exactly the values defined in the JDL.
--
MassimoSgaravatto - 2011-11-07