Tags:
,
view all tags
---+!! Regression Test Work Plan %TOC% ---+ BLAH ---++ [[https://savannah.cern.ch/bugs/?75854][Bug #75854]] Problems related to the growth of the blah registry) %RED%Not implemented%ENDCOLOR% Configure a CREAM CE using the new BLparser. Verify that in /etc/blah.config there is: =job_registry_use_mmap=yes= (default scenario). Submit 5000 jobs on a CREAM CE using the following JDL: <verbatim> [ executable="/bin/sleep"; arguments="100"; ] </verbatim> Monitor the BLAH processed. Verify that each of them doesn't use more than 50 MB. ---++ [[https://savannah.cern.ch/bugs/?77776][Bug #77776]] (BUpdater should have an option to use cached batch system commands) %RED%Not implemented%ENDCOLOR% Add: <verbatim> lsf_batch_caching_enabled=yes batch_command_caching_filter=/usr/bin/runcmd.p </verbatim> in =/etc/blah.config=. Create and fill =/usr/bin/runcmd.pl= with the following content: <verbatim> #!/usr/bin/perl #---------------------# # PROGRAM: argv.pl # #---------------------# $numArgs = $#ARGV + 1; open (MYFILE, '>>/tmp/xyz'); foreach $argnum (0 .. $#ARGV) { print MYFILE "$ARGV[$argnum]\n"; } close (MYFILE); </verbatim> Submit some jobs. Check that in =/tmp/xyz= the queries to the batch system are recorded. E.g. for LSF something like that should be reported: <verbatim> /opt/lsf/7.0/linux2.6-glibc2.3-x86/bin/bjobs -u all -l /opt/lsf/7.0/linux2.6-glibc2.3-x86/bin/bjobs -u all -l ... </verbatim> ---+ CREAM ---++ [[http://savannah.cern.ch/bugs/?69857][Bug #69857]] Job submission to CreamCE is enabled by restart of service even if it was previously disabled - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix: * disable the submission on the CE This can be achieved via the<code> `glite-ce-disable-submission host:port` </code> 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 `<code>glite-ce-enable-submission host:port` </code>command (provided by the CREAM CLI package installed on the UI). Output should be: "Job submission to this CREAM CE is enabled" ---++ [[http://savannah.cern.ch/bugs/?81561][Bug #81561]] Make JobDBAdminPurger script compliant with CREAM EMI environment. - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix, simply run on the CREAM CE as root the JobDBAdminPurger.sh. E.g.: <verbatim> # JobDBAdminPurger.sh -c /etc/glite-ce-cream/cream-config.xml -u <user> -p <passwd> -s DONE-FAILED,0 START jobAdminPurger </verbatim> It should work without reporting error messages: <verbatim> ----------------------------------------------------------- Job CREAM595579358 is going to be purged ... - Job deleted. JobId = CREAM595579358 CREAM595579358 has been purged! ----------------------------------------------------------- STOP jobAdminPurger </verbatim> ---++ [[http://savannah.cern.ch/bugs/?81824][Bug #81824]] yaim-cream-ce should manage the attribute bupdater_loop_interval. - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix, check in the CREAM CE if the file /etc/blah.config contains the parameter bupdater_loop_interval. ---++ [[http://savannah.cern.ch/bugs/?83238][Bug #83238]] Sometimes CREAM does not update the state of a failed job. - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix, try to kill by hand a job. The status of the job should eventually be: <verbatim> Status = [DONE-FAILED] ExitCode = [N/A] FailureReason = [Job has been terminated (got SIGTERM)] </verbatim> ---++ [[http://savannah.cern.ch/bugs/?83749][Bug #83749]] JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - %RED% Not implemented %ENDCOLOR% STATUS: %RED% Not implemented %ENDCOLOR% 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 ---++ [[http://savannah.cern.ch/bugs/?84374][Bug #84374]] yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - %GREEN% Implemented %GREEN% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix, query the resource bdii of the CREAM-CE: <verbatim> ldapsearch -h <CREAM CE host> -x -p 2170 -b "o=grid" | grep -i foreignkey | grep -i glueceuniqueid </verbatim> Entries such as: <verbatim> GlueForeignKey: GlueCEUniqueID=cream-35.pd.infn.it:8443/cream-lsf-creamtest1 </verbatim> i.e.: <verbatim> GlueForeignKey: GlueCEUniqueID=<CREAM CE ID> </verbatim> should appear. ---++ [[http://savannah.cern.ch/bugs/?86191][Bug #86191]] No info published by the lcg-info-dynamic-scheduler for one VOView - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% To test the fix, issue the following ldapsearch query towards the resource bdii of the CREAM-CE: <verbatim> $ ldapsearch -h cream-35 -x -p 2170 -b "o=grid" | grep -i GlueCEStateWaitingJobs | grep -i 444444 </verbatim> It should not find anything ---++ [[http://savannah.cern.ch/bugs/?87361][Bug #87361]] The attribute cream_concurrency_level should be configurable via yaim. - %GREEN% Implemented %ENDCOLOR% STATUS: %GREEN% Implemented %ENDCOLOR% 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: <verbatim> cream_concurrency_level="n" </verbatim> ---++ [[http://savannah.cern.ch/bugs/?87492][Bug #87492]] CREAM doesn't handle correctly the jdl attribute "environment". - %RED% Not implemented %ENDCOLOR% STATUS: %RED% Not implemented %ENDCOLOR% To test the fix, submit the following JDL using =glite-ce-job-submit=: <verbatim> 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"; </verbatim> 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. -- Main.MassimoSgaravatto - 2011-11-07
Edit
|
Attach
|
PDF
|
H
istory
:
r111
|
r12
<
r11
<
r10
<
r9
|
B
acklinks
|
V
iew topic
|
More topic actions...
Topic revision: r10 - 2011-12-19
-
MassimoSgaravatto
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
General Doc
Functional Description
Batch System Support
CREAM and Information Service
Release Notes
Known Issues
Security in CREAM
Nagios Probes to monitor CREAM and WN
Papers
Presentations
User Doc
CREAM User Guide for EMI-1
CREAM User Guide for EMI-2
CREAM User Guide for EMI-3
CREAM JDL Guide
BLAH User Guide
Troubleshooting Guide
System Administrator Doc
System Administrator Guide for CREAM (EMI-3 release)
System Administrator Guide for CREAM (EMI-2 release)
System Administrator Guide for CREAM (EMI-1 release)
The CREAM configuration file
The CEMonitor configuration file
The CREAM CE Service Reference Card (EMI-2 release)
The CREAM CE Service Reference Card (EMI-1 release)
Batch System related documentation
Troubleshooting Guide
The guide for integrating EMIR in CREAM
]
Developers Doc
CREAM Client API C++ Documentation
CREAM Client API for Python
Other Doc
Contacts
Moving to CREAM from LCG-CE
Testing
Internal Collaboration Information
Credits
CREAM Web utilities
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback