Difference: CreamTestsP3179 (27 vs. 28)

Revision 282010-02-26 - MassimoSgaravatto

Line: 1 to 1
 

PATCH 3179

Line: 16 to 16
 
    • Verified in the old blparser log file

  • Bug #45364: BLAH_JOB_CANCEL should report failure reason FIXED
Changed:
<
<
    • submit and cancel a job using the LRMS command (e.g. qdel) and verify that the reason reports "Cancelled by CE admin"
>
>
    • submit a job top CREAM and then cancels it using the LRMS command (e.g. qdel). Before the blparser (and therefore CREAM) realizes that the job was cancelled, issue a glite-ce-job-cancel.
    • Issue a glite-ce-job-status -L 2. For the cancel command a failure )alomng with its reason) should be reported such as:

   *** Command Name              = [JOB_CANCEL]
       Command Category          = [JOB_MANAGEMENT]
       Command Status            = [ERROR]
       Command Fail Reason       = [qdel: Unknown Job Id 45299.cream-38.pd.infn.it]
       Creation Time             = [Fri 26 Feb 2010 18:43:27] (1267206207)
       Start Scheduling Time     = [Fri 26 Feb 2010 18:43:27] (1267206207)
       Start Processing Time     = [Fri 26 Feb 2010 18:43:27] (1267206207)
       Execution Completed Time  = [Fri 26 Feb 2010 18:43:30] (1267206210)
 
  • Bug #46419: CREAM sandbox area should be scratched when the CREAM DB is scratched FIXED
    • Submit at least one job to the CE and wait for its termination, so that the sandbox area is not empty
Changed:
<
<
    • Increment the value of the parameters creamdb_database_version and/or delegationdb_database_version in the file /opt/glite/etc/glite-ce-cream/cream-config.xml.template
>
>
    • Increment the value of the parameters creamdb_database_version in the file /opt/glite/etc/glite-ce-cream/cream-config.xml.template
 
    • reconfigure the node with yaim and check whether the sandbox area is empty
Line: 57 to 69
 
    • verify that the failure reason reported by the job status contains the message: Problem to detect the lifetime of the proxy

  • Bug #51046: CREAM: DelegProxyInfo info sometimes is wrong FIXED
Changed:
<
<
    • submit a job, wait for its termination and verify the correct lifetime of the proxy
>
>
    • submit a job, wait for its termination and verify the correct lifetime of the proxy in the glite-ce-job-status output
 
  • Bug #51118: config_cream_glexec doesn't set glexec permissions right FIXED
    • install a CE node from scratch and verify the permissions for /opt/glite/sbin/glexec (6555) and /opt/glite/etc/glexec.conf (640)
Line: 87 to 99
 
    • check the content of glite-ce-cream rpm

  • Bug #51706: yaim-cream-ce: remove "lcg" prefix from JOB_MANAGER FIXED
Changed:
<
<
    • change the value of JOB_MANAGER in the siteinfo.def
    • configure the node with YAIM and verify that the resource BDII publishes this new value in the GlueCeUniqueids
>
>
    • change the value of JOB_MANAGER in the siteinfo.def e.g. from lsf to lcglsf
    • configure the node with YAIM and verify that in the resource BDII the string lsf (and not lcglsf) appears in the glueeeuniqueids
 
  • Bug #51892: Exception when using java.text.DateFormat.parse 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
Line: 109 to 121
 
  • Bug #52020: [ yaim-cream-ce ] Support use of file (besides syslog) for glexec logging NOT TESTED
Changed:
<
<
  • Bug #52050: misleading error message "The problem seems to be related to glexec INVALID
    • The CREAM service does not make use of glexec anymore
>
>
  • 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
 

  • Bug #52051: CEMon must remove all expired subscriptions on start-up FIXED
Line: 144 to 156
 
  • Bug #53459: [CREAM] Provide method to improve the detection of job status changes by ICE NOT TESTED

  • Bug #53499: CREAM job wrapper template should be put outside the jar FIXED
Changed:
<
<
    • check wheter the file /opt/glite/share/webapps/ce-cream.war contains the file WEB-INF/jobwrapper.tpl
>
>
    • check whether the file /opt/glite/share/webapps/ce-cream.war contains the file WEB-INF/jobwrapper.tpl
 
  • Bug #54812: lsf_submit.sh job requirement FIXED
    • Created (and chmoded +x) the file /opt/glite/bin/lsf_local_submit_attributes.sh on the CREAM CE with the following content:
Line: 162 to 174
 
  • Bug #54949: Some job can remain in running state when BLParser is restarted for both lsf and pbs NOT TESTED
Changed:
<
<
  • Bug #55078: Possible final state not considered in BLParserPBS and BUpdaterPBS NOT TESTED
>
>
  • Bug #55078: Possible final state not considered in BLParserPBS and BUpdaterPBS CANNOT REPRODUCE
    • To test the fix it would be necessary to have a scenario for which in the Torque log file for a certain job the event "Job Run..." is followed by the event "dequeuing from"
    • Not able to reproduce such scenario
 
  • Bug #55420: Allow admin to purge CREAM jobs in a non terminal status FIXED
    • temporary disconnect any WN from the CE, e.g. shutting down the mom server in a TORQUE installation
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback