Difference: RegressionTestWorkPlan (1 vs. 111)

Revision 1112013-10-25 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 645 to 645
 

TODO Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment Not Implemented

#CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment. Not Implemented
Changed:
<
<

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception Not Implemented

>
>

TODO Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception Not Implemented

 #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception. Not Implemented
Changed:
<
<

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring Not Implemented

>
>

TODO Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring Not Implemented

 #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring. Not Implemented

TODO Bug #CREAM-82 Check permission for /var/cream_sandbox Not Implemented

Line: 672 to 672
 
  • during the submission, at ~7000 jobs, execute in parallel several proxy renewal commands referring to the previously delegated user credentials
    > glite-ce-proxy-renew -e cream-27.pd.infn.it:8443 myproxyid
  • check the cream's logs and find the message error "updateDelegationProxyInfo error: Rollback executed due to: Deadlock found when trying to get lock; try restarting transaction": such message should not be present.
Changed:
<
<

Bug #99738 Under stress conditions due to job submissions, the command queue may accumulate thousand of job purging commands Not Implemented

>
>

TODO Bug #99738 Under stress conditions due to job submissions, the command queue may accumulate thousand of job purging commands Not Implemented

 
  • submit ~5000 very short jobs to cream and wait their terminal state (e.g. DONE-OK)
  • edit the cream's configuration file (i.e. /etc/glite-ce-cream/cream-config.xml)
  • change the JOB_PURGE_RATE parameter value to 2 minutes
    <parameter name="JOB_PURGE_RATE" value="2" /> <!-- minutes -->

Revision 1102013-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 605 to 605
 

Bug #CREAM-91 man page missing for glite-ce-job-lease Not Implemented

#CREAM-91 man page missing for glite-ce-job-lease. Not Implemented
Changed:
<
<

Bug #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled Not Implemented

>
>

TODO Bug #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled Not Implemented

 #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled. Not Implemented
Line: 703 to 703
 
  • Check that a message error like the following doesn't appear:
"Received NULL fault; the error is due to another cause: FaultString=[CREAM service not available: configuration failed!] - FaultCode=[SOAP-ENV:Server] - FaultSubCode=[SOAP-ENV:Server]"
Changed:
<
<

Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

>
>

TODO Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

 
  • Create the following two files:

perusal.jdl

Line: 861 to 861
 
  • submit several jobs to CREAM and check if at least one of them has been executed on the previously modified WN (there is no way to force to submission on a specific WN through CREAM)
  • open the StandardError file on the job sandbox: it should contain just the "Cannot find lb_logevent command" message.
Changed:
<
<

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

>
>

TODO Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

 
  • Connect to the ce under test with your pool account user
  • Edit the file /tmp/test_bug94418.sh (as your pool account user) and paste on it the following text:
    #!/bin/bash                                                                                
Line: 906 to 906
 

Fixes provided with CREAM 1.14.1

Changed:
<
<

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

>
>

TODO Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

 
  • on the CREAM node, which MUST be a different machine than the one where is installed the creamdb (DB node), edit the cream-config.xml
  • find the "url" field within the datasource_creamdb element (e.g. url="jdbc:mysql://localhost:3306/creamdb?autoReconnect=true")
Line: 949 to 949
  Example of the error:
GLUE2EndpointURL: https://cream-48.pd.infn.it8443/ce-cream/services
Changed:
<
<

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

>
>

TOREMOVE Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

 
  • create a new local pool account having the name >14 chars size long
  • reconfigure the CE with YAIM (define USE_ARGUS=no if you don't want to configure ARGUS for handling the new local pool account)
Line: 1349 to 1349
 
Changed:
<
<

Bug #86694 A different port number than 9091 should be used for LRMS_EVENT_LISTENER - Not Implemented

>
>

TOREMOVE Bug #86694 A different port number than 9091 should be used for LRMS_EVENT_LISTENER - Not Implemented

  On a running CREAM CE, perform the following command:
Line: 1482 to 1482
 and then configure via yaim. Then query the resource bdii of the CREAM CE and verify that the relevant attributes of the glue2 ComputingManager object are set.
Changed:
<
<

Bug #88078 CREAM DB names should be configurable - Not Implemented

>
>

TOREMOVE Bug #88078 CREAM DB names should be configurable - Not Implemented

  Configure from scratch a CREAM CE setting the yaim variables: CREAM_DB_NAME and DELEGATION_DB_NAME, e.g.:
Line: 1635 to 1635
 
Changed:
<
<

Bug #92338 CREAM load limiter should not disable job submissions when there is no swap space - Not Implemented

>
>

TODO Bug #92338 CREAM load limiter should not disable job submissions when there is no swap space - Not Implemented

  To test the fix, consider a CREAM CE on a machine without swap.

Revision 1092013-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 625 to 625
 

Fixes provided with CREAM 1.14.6

Changed:
<
<

Bug #CREAM-127 - Mount info item not parsed if it contains colon - Not Implemented

>
>

TODOBug #CREAM-127 - Mount info item not parsed if it contains colon - Not Implemented

 #CREAM-127 Mount info item not parsed if it contains colon Not Implemented

Bug #CREAM-113 Enhancement of the CREAM DB API (Sec. Vuln. )Not Implemented

Line: 636 to 636
 

Fixes provided with CREAM 1.14.5

Changed:
<
<

Bug #CREAM-111 Wrong tokenization for epilogue argument list Not Implemented

>
>

TODOBug #CREAM-111 Wrong tokenization for epilogue argument list Not Implemented

 #CREAM-111 Wrong tokenization for epilogue argument list Not Implemented
Changed:
<
<

Bug #CREAM-101 Wrong time format for MaxWallClockTime Not Implemented

>
>

TODOBug #CREAM-101 Wrong time format for MaxWallClockTime Not Implemented

 #CREAM-101 Wrong time format for MaxWallClockTime. Not Implemented
Changed:
<
<

Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment Not Implemented

>
>

TODOBug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment Not Implemented

 #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment. Not Implemented

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception Not Implemented

Line: 651 to 651
 

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring Not Implemented

#CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring. Not Implemented
Changed:
<
<

Bug #CREAM-82 Check permission for /var/cream_sandbox Not Implemented

>
>

TODOBug #CREAM-82 Check permission for /var/cream_sandbox Not Implemented

 #CREAM-82 Check permission for /var/cream_sandbox. Not Implemented

Bug #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin Not Implemented

#CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin. Not Implemented
Changed:
<
<

Bug #CREAM-77 List index error from persistent estimator Not Implemented

>
>

TODOBug #CREAM-77 List index error from persistent estimator Not Implemented

 #CREAM-77 List index error from persistent estimator. Not Implemented

Bug #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()) Not Implemented

Line: 770 to 770
 2013-01-21 17:49:51,196 ERROR - JDL file [pippo.jdl] does not exist. Skipping...
Changed:
<
<

Bug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

>
>

TODOBug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

 
  • in the site-info.def define the variable CE_OTHERDESCR="Cores=10.5 , Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=10.5"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=10.5,Benchmark=8.0", run yaim and verify that an error is reported
Changed:
<
<

Bug #98440 Missing revision number in EndpointImplementationVersion Not Implemented

>
>

TODO Bug #98440 Missing revision number in EndpointImplementationVersion Not Implemented

 
  • run the following command
    ldapsearch -x -H ldap://hostname:2170 -b o=glue '(&(objectclass=GLUE2Endpoint)(GLUE2EndpointImplementationName=CREAM))' GLUE2EndpointImplementationVersion
    and verify that the GLUE2EndpointImplementationVersion reports the revision number
Changed:
<
<

Bug #98850 Empty ACBR list in SHARE variable Not Implemented

>
>

TODO Bug #98850 Empty ACBR list in SHARE variable Not Implemented

 
  • set the YAIM variable FQANVOVIEWS to "no"
  • set one the YAIM variables <QUEUE>_GROUP_ENABLE so that it contains more FQANs for the same VO (for example "atlas /atlas/ROLE=lcgadmin /atlas/ROLE=production /atlas/ROLE=pilot")
Line: 799 to 799
 
  • in the file /etc/my.cnf specify the following value
    max_connections = 256
  • runt the YAIM configurator and verify that the function config_cream_db works correctly
Changed:
<
<

Bug #99282 Wrong regular expression for group.conf parsing Not Implemented

>
>

TODO Bug #99282 Wrong regular expression for group.conf parsing Not Implemented

 
  • define YAIM variables so that one VO name is the prefix or the suffix of another one (for examples VOS=" ops dgops ")
  • run the YAIM configurator and verify that in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif no references to one VO appear as attributes of the Shares or Policies of the other
Changed:
<
<

Bug #99747 glite-info-dynamic-ce does not update GLUE2ComputingShareServingState Not Implemented

>
>

TODOBug #99747 glite-info-dynamic-ce does not update GLUE2ComputingShareServingState Not Implemented

 
  • disable the submissions to the CE
  • run the command
    /sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-cream-glue2" |grep ServingState
Line: 820 to 820
 

Fixes provided with CREAM 1.14.2

Changed:
<
<

Bug #95328 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

>
>

TODOBug #95328 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

 
  • Configure a CREAM CE in cluster mode, run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GlueCE | grep InfoHostName
    and verify that one or more items exists.
Changed:
<
<

Bug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

>
>

TODOBug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

 
  • Define the YAIM variable CE_CAPABILITY="CPUScalingReferenceSI00=10 SNMPSupport=yes"
  • Configure with YAIM and run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep GLUE2EntityOtherInfo
Line: 998 to 998
 
Changed:
<
<

Bug #68968 lcg-info-dynamic-software should protect against duplicate RTE tags - Not Implemented

>
>

TODOBug #68968 lcg-info-dynamic-software should protect against duplicate RTE tags - Not Implemented

  To verify the fix edit a VO.list file under /opt/glite/var/info/cream-38.pd.infn.it/VO adding:
Line: 1023 to 1023
 
Changed:
<
<

Bug #69854 CreamCE should publish non-production state when job submission is disabled - Not Implemented

>
>

TODO Bug #69854 CreamCE should publish non-production state when job submission is disabled - Not Implemented

  Disable job submission with glite-ce-disable-submission. Wait 3 minutes and then perform the following ldap query:
Line: 1093 to 1093
 
Changed:
<
<

Bug #79362 location of python files provided with lcg-info-dynamic-scheduler-generic-2.3.5-0.sl5 - Not Implemented

>
>

TOREMOVEBug #79362 location of python files provided with lcg-info-dynamic-scheduler-generic-2.3.5-0.sl5 - Not Implemented - obsolete

  To verify the fix, do a:
Line: 1104 to 1104
 and verify that the files are installed in usr/lib/python2.4 and not more in /usr/lib/python.
Changed:
<
<

Bug #80295 Allow dynamic scheduler to function correctly when login shell is false - Not Implemented

>
>

TOREMOVEBug #80295 Allow dynamic scheduler to function correctly when login shell is false - Not Implemented - overriden by https://savannah.cern.ch/bugs/?99747

  To verify the fix, log on the CREAM CE as user root and run:
Line: 1257 to 1257
  Consider the same test done for bug #83592
Changed:
<
<

Bug #84308 Error on glite_cream_load_monitor if cream db is on another host - Not Implemented

>
>

TODOBug #84308 Error on glite_cream_load_monitor if cream db is on another host - Not Implemented

  Configure a CREAM CE with the database installed on a different host than the CREAM CE.
Line: 1282 to 1282
  and not like the one reported in the savannah bug.
Changed:
<
<

Bug #86609 yaim variable CE_OTHERDESCR not properly managed for Glue2 - Not Implemented

>
>

TOREMOVEBug #86609 yaim variable CE_OTHERDESCR not properly managed for Glue2 - Not Implemented - merge with https://savannah.cern.ch/bugs/?95041

  Try to set the yaim variable CE_OTHERDESCR to:
Line: 1428 to 1428
 
Changed:
<
<

Bug #87690 Not possible to map different queues to different clusters for CREAM configured in cluster mode - Not Implemented

>
>

TOREMOVE Bug #87690 Not possible to map different queues to different clusters for CREAM configured in cluster mode - Not Implemented - just one cluster supported

  Configure via yaim a CREAM CE in cluster mode with different queues mapped to different clusters, e.g.:
Line: 1528 to 1528
 INFO: Executing function: config_cream_gip_scheduler_plugin_check
Changed:
<
<

Bug #89664 yaim-cream-ce doesn't manage spaces in CE_OTHERDESCR - Not Implemented

>
>

TOREMOVEBug #89664 yaim-cream-ce doesn't manage spaces in CE_OTHERDESCR - Not Implemented - merge with https://savannah.cern.ch/bugs/?95041

 

Try to set the yaim variable CE_OTHERDESCR to:

Line: 1618 to 1618
  Tested through the limiter test of the Robot based test-suite
Changed:
<
<

Bug #92102 Tomcat attributes in the CREAM CE should be configurable via yaim - Not Implemented

>
>

TODO Bug #92102 Tomcat attributes in the CREAM CE should be configurable via yaim - Not Implemented

  Set in siteinfo.def:
Line: 1928 to 1928
 

Fixes provided with CREAM TORQUE module 2.1.2

Changed:
<
<

CREAM #119 - Wrong total cpu count from PBS infoprovider Not Implemented

>
>

TODOCREAM #119 - Wrong total cpu count from PBS infoprovider Not Implemented

 CREAM #119 Wrong total cpu count from PBS infoprovider Not Implemented

Fixes provided with CREAM TORQUE module 2.1.1

Line: 1942 to 1942
 

Fixes provided with CREAM TORQUE module 2.0.1

Changed:
<
<

Bug #95184 Missing real value for GlueCEPolicyMaxSlotsPerJob Not Implemented

>
>

TODOBug #95184 Missing real value for GlueCEPolicyMaxSlotsPerJob Not Implemented

 
  • configure the TORQUE server so that the parameter "resources_max.procct" for a given queue is defined and greater than zero
  • run the script /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
  • verify that the attribute GlueCEPolicyMaxSlotsPerJob for the given queue reports the value of the parameter above
Changed:
<
<

Bug #96636 Time limits for GLUE 2 are different to GLUE 1 Not Implemented

>
>

TODOBug #96636 Time limits for GLUE 2 are different to GLUE 1 Not Implemented

 
  • run the command
    ldapsearch -x -H ldap://hostname:2170 -b o=glue '(&(objectclass=GLUE2ComputingShare))' [attributeName] 
    where attributeName is one of the following arguments: GLUE2ComputingShareMaxCPUTime, GLUE2ComputingShareMaxWallTime, GLUE2ComputingShareDefaultCPUTime, GLUE2ComputingShareDefaultWallTime
Line: 1958 to 1958
  where attributeName is one of the following arguments: GlueCEPolicyMaxCPUTime, GlueCEPolicyMaxObtainableCPUTime, GlueCEPolicyMaxWallClockTime, GlueCEPolicyMaxObtainableWallClockTime
  • verify that each value, if available, is expressed in minutes
Changed:
<
<

Bug #99639 lcg-info-dynamic-scheduler-pbs cannot parse qstat output with spurious lines Not Implemented

>
>

TODOBug #99639 lcg-info-dynamic-scheduler-pbs cannot parse qstat output with spurious lines Not Implemented

 
  • save the output of the command
    qstat -f
    in a temporary file
  • insert several spurious lines within the block of job data, it's better to insert also some empty lines.
Line: 2006 to 2006
 Verify that the published value for GlueCEPolicyMaxCPUTime is the minimum between D and F.
Changed:
<
<

Bug #76162 YAIM for APEL parsers to use the BATCH_LOG_DIR for the batch system log location - Not implemented

>
>

TOREMOVEBug #76162 YAIM for APEL parsers to use the BATCH_LOG_DIR for the batch system log location - Not implemented - obsolete

  To test the fix for this bug, set the yaim variable BATCH_ACCT_DIR and configure via yaim.
Line: 2024 to 2024
 Check the file /etc/glite-apel-pbs/parser-config-yaim.xml and verify that the directory name is ${TORQUE_VAR_DIR}/server_priv/accounting
Changed:
<
<

Bug #77106 PBS info provider doesn't allow - in a queue name - Not implemented

>
>

TOREMOVEBug #77106 PBS info provider doesn't allow - in a queue name - Not implemented - obsolete

  To test the fix, configure a CREAM CE in a PBS installation where at least a queue has a - in its name.

Revision 1082013-10-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 623 to 623
 
Added:
>
>

Fixes provided with CREAM 1.14.6

 
Added:
>
>

Bug #CREAM-127 - Mount info item not parsed if it contains colon - Not Implemented

#CREAM-127 Mount info item not parsed if it contains colon Not Implemented

Bug #CREAM-113 Enhancement of the CREAM DB API (Sec. Vuln. )Not Implemented

#CREAM-113 Enhancement of the CREAM DB API Not Implemented

Bug #CREAM-124 Fix a bug related to gridsite (Sec. Vuln. )Not Implemented

#CREAM-124 Fix a bug related to gridsite Not Implemented
 

Fixes provided with CREAM 1.14.5

Line: 1916 to 1925
 

CREAM Torque module

Added:
>
>

Fixes provided with CREAM TORQUE module 2.1.2

CREAM #119 - Wrong total cpu count from PBS infoprovider Not Implemented

CREAM #119 Wrong total cpu count from PBS infoprovider Not Implemented
 

Fixes provided with CREAM TORQUE module 2.1.1

CREAM #101 - Wrong time format for MaxWallClockTime Not Implemented

Line: 2081 to 2096
  yaim installation should fail saying that there were problems with LSF installation.
Added:
>
>

CREAM SLURM module

Fixes provided with CREAM SLURM module 1.0.1

CREAM #116 - Missing CE information from SLURM infoprovider Not Implemented

CREAM #116 Missing CE information from SLURM infoprovider Not Implemented
 
META PREFERENCE name="ALLOWTOPICCHANGE" title="ALLOWTOPICCHANGE" type="Set" value="CristinaAiftimiei"

Revision 1072013-10-10 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 7 to 7
 

BLAH

Added:
>
>

Fixes provided with BLAH 1.20.3

Bug #CREAM-112 sge_local_submit_attributes.sh problem with memory requirements Not Implemented

#CREAM-112 sge_local_submit_attributes.sh problem with memory requirements. Not Implemented

 

Fixes provided with BLAH 1.20.2

Bug #CREAM-88 Memory leak in BNotifier Not Implemented

Line: 543 to 550
 

CREAM

Added:
>
>

Fixes provided with CREAM 1.16.2

Bug #CREAM-113 Enhancement of the CREAM DB API (Sec. Vuln. )Not Implemented

#CREAM-113 Enhancement of the CREAM DB API Not Implemented

Bug #CREAM-124 Fix a bug related to gridsite (Sec. Vuln. )Not Implemented

#CREAM-124 Fix a bug related to gridsite Not Implemented

Bug #CREAM-125 SOAP Header is not set Not Implemented

#CREAM-125 SOAP Header is not set Not Implemented
 

Fixes provided with CREAM 1.16.1

Bug #CREAM-107 Bad timezone format Not Implemented

Line: 1898 to 1916
 

CREAM Torque module

Added:
>
>

Fixes provided with CREAM TORQUE module 2.1.1

CREAM #101 - Wrong time format for MaxWallClockTime Not Implemented

CREAM #101 Wrong time format for MaxWallClockTime Not Implemented

CREAM #107 - Bad timezone format Not Implemented

CREAM #107 Bad timezone format Not Implemented
 

Fixes provided with CREAM TORQUE module 2.0.1

Line: 2012 to 2037
 

CREAM LSF module

Added:
>
>

Fixes provided with CREAM LSF module 2.0.3

CREAM #114 - Execution error: Uncaught exception Not Implemented

CREAM #114 Execution error: Uncaught exception Not Implemented
 

Bug #88720 Too many '9' in GlueCEPolicyMaxCPUTime for LSF - Not implemented

To test the fix, query the CREAM CE resource bdii in the following way:

Revision 1062013-09-24 - TWikiAdminUser

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 2050 to 2050
 To test the fix, configure a CREAM CE without having also installed LSF.

yaim installation should fail saying that there were problems with LSF installation.

Changed:
<
<
META PREFERENCE name="ALLOWTOPICCHANGE" title="ALLOWTOPICCHANGE" type="Set" value="TWikiAdminUser CreamGroup"
>
>
META PREFERENCE name="ALLOWTOPICCHANGE" title="ALLOWTOPICCHANGE" type="Set" value="CristinaAiftimiei"

Revision 1052013-09-24 - TWikiAdminUser

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 2050 to 2050
 To test the fix, configure a CREAM CE without having also installed LSF.

yaim installation should fail saying that there were problems with LSF installation.

Added:
>
>
META PREFERENCE name="ALLOWTOPICCHANGE" title="ALLOWTOPICCHANGE" type="Set" value="TWikiAdminUser CreamGroup"

Revision 1042013-07-22 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 19 to 19
 #CREAM-105 Env vars in blah.config should be exported also in daemons. Not Implemented
Added:
>
>

Fixes provided with BLAH 1.18.4

Bug #CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh Not Implemented

#CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh. Not Implemented

Bug #CREAM-105 Env vars in blah.config should be exported also in daemons Not Implemented

#CREAM-105 Env vars in blah.config should be exported also in daemons. Not Implemented

Bug #CREAM-112 sge_local_submit_attributes.sh problem with memory requirements Not Implemented

#CREAM-112 sge_local_submit_attributes.sh problem with memory requirements Not Implemented
 

Fixes provided with BLAH 1.18.2

Line: 532 to 543
 

CREAM

Changed:
<
<

Fixes provided with CREAM 1.16.0

>
>

Fixes provided with CREAM 1.16.1

 

Bug #CREAM-107 Bad timezone format Not Implemented

#CREAM-107 Bad timezone format. Not Implemented
Line: 592 to 603
 
  • Verify that the files ce-cream-es.xml and ce-monitor.xml are not present in the directory /etc/tomcat6/Catalina/localhost/
  • Increase the verbosity of the CREAM log from info to debug, restart the service, submit a big bunch of jobs and verify that the size of a log file is about 1Mb.
Added:
>
>

Fixes provided with CREAM 1.14.5

Bug #CREAM-111 Wrong tokenization for epilogue argument list Not Implemented

#CREAM-111 Wrong tokenization for epilogue argument list Not Implemented

Bug #CREAM-101 Wrong time format for MaxWallClockTime Not Implemented

#CREAM-101 Wrong time format for MaxWallClockTime. Not Implemented

Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment Not Implemented

#CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment. Not Implemented

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception Not Implemented

#CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception. Not Implemented

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring Not Implemented

#CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring. Not Implemented

Bug #CREAM-82 Check permission for /var/cream_sandbox Not Implemented

#CREAM-82 Check permission for /var/cream_sandbox. Not Implemented

Bug #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin Not Implemented

#CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin. Not Implemented

Bug #CREAM-77 List index error from persistent estimator Not Implemented

#CREAM-77 List index error from persistent estimator. Not Implemented

Bug #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()) Not Implemented

#CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()). Not Implemented
 

Fixes provided with CREAM 1.14.3

Bug #99740 updateDelegationProxyInfo error: Rollback executed due to Deadlock Not Implemented

Revision 1032013-06-28 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Added:
>
>

Fixes provided with BLAH 1.20.2

Bug #CREAM-88 Memory leak in BNotifier Not Implemented

#CREAM-88 Memory leak in BNotifier. Not Implemented

Bug #CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh Not Implemented

#CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh. Not Implemented

Bug #CREAM-105 Env vars in blah.config should be exported also in daemons Not Implemented

#CREAM-105 Env vars in blah.config should be exported also in daemons. Not Implemented
 

Fixes provided with BLAH 1.18.2

Line: 521 to 534
 

Fixes provided with CREAM 1.16.0

Changed:
<
<

Bug #CREAM-107 Bad timezone format

>
>

Bug #CREAM-107 Bad timezone format Not Implemented

 #CREAM-107 Bad timezone format. Not Implemented
Changed:
<
<

Bug #CREAM-103 Wrong symlinks upgrading from EMI-2 to EMI-3

>
>

Bug #CREAM-103 Wrong symlinks upgrading from EMI-2 to EMI-3 Not Implemented

 #CREAM-103 Wrong symlinks upgrading from EMI-2 to EMI-3. Not Implemented
Changed:
<
<

Bug #CREAM-101 Wrong time format for MaxWallClockTime

>
>

Bug #CREAM-101 Wrong time format for MaxWallClockTime Not Implemented

 #CREAM-101 Wrong time format for MaxWallClockTime. Not Implemented
Changed:
<
<

Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment

>
>

Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment Not Implemented

 #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment. Not Implemented
Changed:
<
<

Bug #CREAM-82 Check permission for /var/cream_sandbox

>
>

Bug #CREAM-82 Check permission for /var/cream_sandbox Not Implemented

 #CREAM-82 Check permission for /var/cream_sandbox. Not Implemented
Changed:
<
<

Bug #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin

>
>

Bug #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin Not Implemented

 #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin. Not Implemented
Changed:
<
<

Bug #CREAM-77 List index error from persistent estimator

>
>

Bug #CREAM-77 List index error from persistent estimator Not Implemented

 #CREAM-77 List index error from persistent estimator. Not Implemented
Changed:
<
<

Bug #CREAM-74 Remove trustmanager from the provides list of cream-common

>
>

Bug #CREAM-74 Remove trustmanager from the provides list of cream-common Not Implemented

 #CREAM-74 Remove trustmanager from the provides list of cream-common. Not Implemented
Changed:
<
<

Bug #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace())

>
>

Bug #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()) Not Implemented

 #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()). Not Implemented
Changed:
<
<

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring

>
>

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring Not Implemented

 #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring. Not Implemented
Changed:
<
<

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception

>
>

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception Not Implemented

 #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception. Not Implemented
Changed:
<
<

Bug #CREAM-88 Memory leak in BNotifier

#CREAM-88 Memory leak in BNotifier. Not Implemented

Bug #CREAM-89 --leaseId option doesn't work

>
>

Bug #CREAM-89 --leaseId option doesn't work Not Implemented

 #CREAM-89 --leaseId option doesn't work. Not Implemented
Changed:
<
<

Bug #CREAM-90 --help option doesn't work on glite-ce-job-submit and glite-ce-event-query

>
>

Bug #CREAM-90 --help option doesn't work on glite-ce-job-submit and glite-ce-event-query Not Implemented

 #CREAM-90 --help option doesn't work on glite-ce-job-submit and glite-ce-event-query. Not Implemented
Changed:
<
<

Bug #CREAM-91 man page missing for glite-ce-job-lease

>
>

Bug #CREAM-91 man page missing for glite-ce-job-lease Not Implemented

 #CREAM-91 man page missing for glite-ce-job-lease. Not Implemented
Changed:
<
<

Bug #CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh

#CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh. Not Implemented

Bug #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled

>
>

Bug #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled Not Implemented

 #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled. Not Implemented
Deleted:
<
<

Bug #CREAM-105 Env vars in blah.config should be exported also in daemons

#CREAM-105 Env vars in blah.config should be exported also in daemons. Not Implemented
 

Fixes provided with CREAM 1.15.2

Line: 1741 to 1737
 

Fixes provided with glite-CLUSTER v. 2.0.1

Changed:
<
<

Bug #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration

>
>

Bug #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration Not Implemented

 #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented
Changed:
<
<

Bug #CREAM-98 Generated configuration files conflict with CREAM ones

>
>

Bug #CREAM-98 Generated configuration files conflict with CREAM ones Not Implemented

 #CREAM-98 Generated configuration files conflict with CREAM ones Not implemented
Changed:
<
<

Bug #CREAM-100 Remove lcg prefix from template

>
>

Bug #CREAM-100 Remove lcg prefix from template Not Implemented

 [https://issues.infn.it/jira/browse/CREAM-100?focusedCommentId=29883&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-29883][#CREAM-100]] Remove lcg prefix from template Not implemented
Changed:
<
<

Bug #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation

>
>

Bug #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation Not Implemented

 #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation Not implemented
Changed:
<
<

Bug #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode

>
>

Bug #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not Implemented

 #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented

Revision 1022013-06-27 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 553 to 553
  #CREAM-74 Remove trustmanager from the provides list of cream-common. Not Implemented
Added:
>
>

Bug #CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace())

#CREAM-75 CREAM should avoid to log the error messages by including even the full stack trace (i.e printStackTrace()). Not Implemented
 
Added:
>
>

Bug #CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring

#CREAM-83 CREAM should be able to immediately kill also queued jobs, when the proxy is expiring. Not Implemented

Bug #CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception

#CREAM-84 The DelegationPurger may cause a java.lang.OutOfMemoryError exception. Not Implemented

Bug #CREAM-88 Memory leak in BNotifier

#CREAM-88 Memory leak in BNotifier. Not Implemented

Bug #CREAM-89 --leaseId option doesn't work

#CREAM-89 --leaseId option doesn't work. Not Implemented

Bug #CREAM-90 --help option doesn't work on glite-ce-job-submit and glite-ce-event-query

#CREAM-90 --help option doesn't work on glite-ce-job-submit and glite-ce-event-query. Not Implemented

Bug #CREAM-91 man page missing for glite-ce-job-lease

#CREAM-91 man page missing for glite-ce-job-lease. Not Implemented

Bug #CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh

#CREAM-94 Command not found error in /usr/libexec/sge_cancel.sh. Not Implemented

Bug #CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled

#CREAM-102 cream job-wrapper gets stuck in EMI-3 if perusal is enabled. Not Implemented

Bug #CREAM-105 Env vars in blah.config should be exported also in daemons

#CREAM-105 Env vars in blah.config should be exported also in daemons. Not Implemented
 

Revision 1012013-06-27 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 519 to 519
 

CREAM

Added:
>
>

Fixes provided with CREAM 1.16.0

Bug #CREAM-107 Bad timezone format

#CREAM-107 Bad timezone format. Not Implemented

Bug #CREAM-103 Wrong symlinks upgrading from EMI-2 to EMI-3

#CREAM-103 Wrong symlinks upgrading from EMI-2 to EMI-3. Not Implemented

Bug #CREAM-101 Wrong time format for MaxWallClockTime

#CREAM-101 Wrong time format for MaxWallClockTime. Not Implemented

Bug #CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment

#CREAM-99 Python error on ERT calculation: local variable 'est' referenced before assignment. Not Implemented

Bug #CREAM-82 Check permission for /var/cream_sandbox

#CREAM-82 Check permission for /var/cream_sandbox. Not Implemented

Bug #CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin

#CREAM-78 Check for /etc/lrms in config_cream_gip_scheduler_plugin. Not Implemented

Bug #CREAM-77 List index error from persistent estimator

#CREAM-77 List index error from persistent estimator. Not Implemented

Bug #CREAM-74 Remove trustmanager from the provides list of cream-common

#CREAM-74 Remove trustmanager from the provides list of cream-common. Not Implemented

 

Fixes provided with CREAM 1.15.2

Bug #101221 CREAM sends wrong authorization requests to Argus containing attributes with empty values. Not Implemented

Line: 1662 to 1713
 

Fixes provided with glite-CLUSTER v. 2.0.1

Changed:
<
<
  • #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented
  • #CREAM-98 Generated configuration files conflict with CREAM ones Not implemented
  • #CREAM-100 Remove lcg prefix from template Not implemented
  • #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation Not implemented
  • #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented
>
>

Bug #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration

#CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented

Bug #CREAM-98 Generated configuration files conflict with CREAM ones

#CREAM-98 Generated configuration files conflict with CREAM ones Not implemented

Bug #CREAM-100 Remove lcg prefix from template

[https://issues.infn.it/jira/browse/CREAM-100?focusedCommentId=29883&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-29883][#CREAM-100]] Remove lcg prefix from template Not implemented

Bug #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation

#CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation Not implemented

Bug #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode

#CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented

 

Fixes provided with previous versions

Revision 1002013-06-27 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 517 to 517
 


Added:
>
>

CREAM

 

Fixes provided with CREAM 1.15.2

Revision 992013-06-17 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1661 to 1661
 

Fixes provided with glite-CLUSTER v. 2.0.1

Changed:
<
<

Bug #99745 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented

  • Install and configure a glite-CLUSTER node with at least two subclusters; specify two different values for one YAIM subcluster variable (for example SUBCLUSTER_subcluster-identifier_HOST_BenchmarkSF00)
  • Verify that the values published for each subcluster are correct, following the example above the attributes GlueHostBenchmarkSF00 must be different for the two subcluster

Bug #99750 Generated configuration files conflict with CREAM ones Not implemented

  • Install emi-cream-ce and emi-cluster on the same machine
  • Run YAIM configurator specifying the two nodes: -n creamCE -n glite-CLUSTER
  • Verify that the attributes GLUE2EndpointHealthState and GLUE2EndpointHealthStateInfo for the CREAM GLUE2 Computing Endpoint are correctly published

Bug #99824 Remove lcg prefix from template Not implemented

Verify that the file /opt/glite/yaim/examples/siteinfo/services/glite-cluster contains the following comment:

# The name of the job manager used by the gatekeeper
# This variable has been renamed in the new infosys configuration.
# The old variable name was: JOB_MANAGER
# Please, define: pbs, lfs, sge or condor 
#CE_HOST_<hostname>_CE_InfoJobManager=my_job_manager

Bug #100061 Wrong GLUE output format in a CREAM+Cluster installation Not implemented

  • Install emi-cream-ce and emi-cluster on the same machine
  • Run YAIM configurator specifying the two nodes: -n creamCE -n glite-CLUSTER
  • Submit some jobs to the CREAM CE
  • Verify that the Glue1 attributes GlueCEStateFreeJobSlots, GlueCEStateRunningJobs and GlueCEStateWaitingJobs are correctly published
  • Verify that the Glue2 attributes GLUE2ComputingShareFreeSlots, GLUE2ComputingShareWaitingJobs and GLUE2ComputingShareRunningJobs are correctly published
  • Install and configure emi-cream-ce and emi-cluster on different machines
  • Submit some jobs to the CREAM CE
  • Verify that the Glue1 attributes GlueCEStateFreeJobSlots, GlueCEStateRunningJobs and GlueCEStateWaitingJobs are correctly published by the resource BDII on the CREAM node
  • Verify that the Glue2 attributes GLUE2ComputingShareFreeSlots, GLUE2ComputingShareWaitingJobs and GLUE2ComputingShareRunningJobs are correctly published by the resource BDII on the cluster node

Bug #100395 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented

  • Install and configure a CREAM node in cluster mode, removing all the CE_* variables from the site-info.def but the CE_SMPSIZE one (use variables SUBCLUSTER_subclusterid_HOST_* instead)
  • Verify that YAIM configurator reports no errors
>
>
  • #CREAM-96 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented
  • #CREAM-98 Generated configuration files conflict with CREAM ones Not implemented
  • #CREAM-100 Remove lcg prefix from template Not implemented
  • #CREAM-97 Wrong GLUE output format in a CREAM+Cluster installation Not implemented
  • #CREAM-95 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented
 

Fixes provided with previous versions

Revision 982013-04-19 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 520 to 520
 

Fixes provided with CREAM 1.15.2

Added:
>
>

Bug #101221 CREAM sends wrong authorization requests to Argus containing attributes with empty values. Not Implemented

  • The bug is not reproducible because it is triggered out just by the certificate of a specific user
 

Bug #101108 Minor issues from INFN-T1 Not Implemented

  • On SL6 host install and configure with YAIM the CREAM CE disabling both ES and CEMonitor
  • In the YAIM log verify that the tomcat server has been restarted just twice, the first time for the configuration of all Web-Services and then for the configuration of secure-tomcat

Revision 972013-04-18 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 518 to 518
 
Added:
>
>

Fixes provided with CREAM 1.15.2

Bug #101108 Minor issues from INFN-T1 Not Implemented

  • On SL6 host install and configure with YAIM the CREAM CE disabling both ES and CEMonitor
  • In the YAIM log verify that the tomcat server has been restarted just twice, the first time for the configuration of all Web-Services and then for the configuration of secure-tomcat
  • Verify that the files ce-cream-es.xml and ce-monitor.xml are not present in the directory /etc/tomcat6/Catalina/localhost/
  • Increase the verbosity of the CREAM log from info to debug, restart the service, submit a big bunch of jobs and verify that the size of a log file is about 1Mb.
 

Fixes provided with CREAM 1.14.3

Bug #99740 updateDelegationProxyInfo error: Rollback executed due to Deadlock Not Implemented

Revision 962013-03-20 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1650 to 1650
 

Fixes provided with glite-CLUSTER v. 2.0.1

Added:
>
>

Bug #99745 CLUSTER Yaim generates incorrect Subcluster configuration Not implemented

  • Install and configure a glite-CLUSTER node with at least two subclusters; specify two different values for one YAIM subcluster variable (for example SUBCLUSTER_subcluster-identifier_HOST_BenchmarkSF00)
  • Verify that the values published for each subcluster are correct, following the example above the attributes GlueHostBenchmarkSF00 must be different for the two subcluster
 

Bug #99750 Generated configuration files conflict with CREAM ones Not implemented

  • Install emi-cream-ce and emi-cluster on the same machine

Revision 952013-03-13 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1648 to 1648
 

gLite-CLUSTER

Changed:
<
<

Bug #69318 The cluster publisher needs to publish in GLUE 2 too Not implemented

>
>

Fixes provided with glite-CLUSTER v. 2.0.1

Bug #99750 Generated configuration files conflict with CREAM ones Not implemented

  • Install emi-cream-ce and emi-cluster on the same machine
  • Run YAIM configurator specifying the two nodes: -n creamCE -n glite-CLUSTER
  • Verify that the attributes GLUE2EndpointHealthState and GLUE2EndpointHealthStateInfo for the CREAM GLUE2 Computing Endpoint are correctly published

Bug #99824 Remove lcg prefix from template Not implemented

Verify that the file /opt/glite/yaim/examples/siteinfo/services/glite-cluster contains the following comment:

# The name of the job manager used by the gatekeeper
# This variable has been renamed in the new infosys configuration.
# The old variable name was: JOB_MANAGER
# Please, define: pbs, lfs, sge or condor 
#CE_HOST_<hostname>_CE_InfoJobManager=my_job_manager

Bug #100061 Wrong GLUE output format in a CREAM+Cluster installation Not implemented

  • Install emi-cream-ce and emi-cluster on the same machine
  • Run YAIM configurator specifying the two nodes: -n creamCE -n glite-CLUSTER
  • Submit some jobs to the CREAM CE
  • Verify that the Glue1 attributes GlueCEStateFreeJobSlots, GlueCEStateRunningJobs and GlueCEStateWaitingJobs are correctly published
  • Verify that the Glue2 attributes GLUE2ComputingShareFreeSlots, GLUE2ComputingShareWaitingJobs and GLUE2ComputingShareRunningJobs are correctly published
  • Install and configure emi-cream-ce and emi-cluster on different machines
  • Submit some jobs to the CREAM CE
  • Verify that the Glue1 attributes GlueCEStateFreeJobSlots, GlueCEStateRunningJobs and GlueCEStateWaitingJobs are correctly published by the resource BDII on the CREAM node
  • Verify that the Glue2 attributes GLUE2ComputingShareFreeSlots, GLUE2ComputingShareWaitingJobs and GLUE2ComputingShareRunningJobs are correctly published by the resource BDII on the cluster node

Bug #100395 CE_* YAIM variables not mandatory for GLUE2 in cluster mode Not implemented

  • Install and configure a CREAM node in cluster mode, removing all the CE_* variables from the site-info.def but the CE_SMPSIZE one (use variables SUBCLUSTER_subclusterid_HOST_* instead)
  • Verify that YAIM configurator reports no errors

Fixes provided with previous versions

Bug #69318 The cluster publisher needs to publish in GLUE 2 too Not implemented

 
Line: 1679 to 1715
 ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"
Changed:
<
<

Bug #86512 YAIM CLuster Publisher incorrectly configures GlueClusterService and GlueForeignKey for CreamCEs- Not implemented

>
>

Bug #86512 YAIM CLuster Publisher incorrectly configures GlueClusterService and GlueForeignKey for CreamCEs- Not implemented

  To test the fix issue a ldapsearch such as:
Line: 1700 to 1736
 
Changed:
<
<

Bug #87691 Not possible to map different queues of the same CE to different clusters - Not implemented

>
>

Bug #87691 Not possible to map different queues of the same CE to different clusters - Not implemented

  To test this fix, configure a gLite-CLUSTER with at least two different queues mapped to different clusters (use the yaim variables QUEUE__CLUSTER_UniqueID), e.g."
Line: 1716 to 1752
 
  • for the GlueCluster objectclass with GlueClusterUniqueID equal to cl2id, the attributes GlueClusterService and GlueForeignKey refers to CEIds with creamtest2 as queue

Changed:
<
<

Bug #87799 Add yaim variables to configure the GLUE 2 WorkingArea attributes - Not implemented

>
>

Bug #87799 Add yaim variables to configure the GLUE 2 WorkingArea attributes - Not implemented

  Set all (or some) of the following yaim variables:

Revision 942013-02-07 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 661 to 661
 

Bug #99747 glite-info-dynamic-ce does not update GLUE2ComputingShareServingState Not Implemented

  • disable the submissions to the CE
Changed:
<
<
  • run the command
    /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
>
>
  • run the command
    /sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-cream-glue2" |grep ServingState
 
  • verify that the values for each "GLUE2ComputingShareServingState" are set to "draining"

Bug #99823 SHA-1 algorithm for PKCS10 generation in CREAM delegation service Not Implemented

Revision 932013-02-01 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1768 to 1768
 

Bug #99639 lcg-info-dynamic-scheduler-pbs cannot parse qstat output with spurious lines Not Implemented

  • save the output of the command
    qstat -f
    in a temporary file
Changed:
<
<
  • insert a spurious line within the block of job data
>
>
  • insert several spurious lines within the block of job data, it's better to insert also some empty lines.
 
  • run the command
    lcg-info-dynamic-scheduler-pbs -c [temporary file]
  • verify that the execution works fine

Revision 922013-01-22 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 699 to 699
 
  • Run the wrapper script /var/lib/bdii/gip/plugin/glite-info-dynamic-software-wrapper
  • Verify that no duplicated attributes are printed on the stdout
Changed:
<
<

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Not Implemented

>
>

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Implemented

 
  • 1) access to the CREAM DB
  • 2) execute the following SQL command:
    use creamdb;
  • 3) execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;

Revision 912013-01-22 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 558 to 558
 
"Received NULL fault; the error is due to another cause: FaultString=[CREAM service not available: configuration failed!] - FaultCode=[SOAP-ENV:Server] - FaultSubCode=[SOAP-ENV:Server]"

Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

Added:
>
>
  • Create the following two files:

perusal.jdl

[
Type="Job";
JobType="Normal";
Executable = "perusal.sh";
StdOutput = "stdout.log";
StdError = "stderr.log";
InputSandbox = "perusal.sh";
OutputSandbox = {"stdout.log", "stderr.log", "results.txt"};
PerusalFilesDestURI="gsiftp://cream-05.pd.infn.it/tmp";
PerusalFileEnable = true;
PerusalTimeInterval = 20;
outputsandboxbasedesturi="gsiftp://localhost";
PerusalListFileURI="gsiftp://cream-05.pd.infn.it/tmp/filelist.txt"
]

perusal.sh

#!/bin/sh
i=0
while ((i < 10))
do
date
voms-proxy-info --all >&2
df >> results.txt
sleep 10
let "i++"
echo i = $i
done

N.B: For this test, the file "gsiftp://cream-05.pd.infn.it/tmp/filelist.txt" must not exist!

  • Submit the job

  • Check that after about two minutes, the job terminated successfully.
 

Bug #95637 glite-ce-job-submit --help doesn't print out anything Not Implemented

  • execute the command:
    glite-ce-job-submit --help

Revision 902013-01-21 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 565 to 560
 

Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

Bug #95637 glite-ce-job-submit --help doesn't print out anything Not Implemented

Added:
>
>
  • execute the command:
    glite-ce-job-submit --help
  • the error message "JDL file not specified in the command line arguments. Stop." should not appear anymore. In place, the inline help is shown:
    >glite-ce-job-submit --help
    CREAM User Interface version 1.2.0
    
    glite-ce-job-submit allows the user to submit a job for execution on a CREAM based CE
    
    Usage: glite-ce-job-submit [options] -r <CEID> <JDLFile>
    
      --resource, -r CEID  Select the CE to send the JDL to. Format must be <host>[:<port>]/cream-<lrms-system-name>-<queue-name>
    
      <JDLFile>  Is the file containing the JDL directives for job submission;
    
    Options:
      --help, -h                
    [...]
 

Bug #95738 glite-ce-job-submit: error message to be improved if JDL file is missing Not Implemented

Added:
>
>
  • execute the command (remark: the test.jdl file doesn't exist):
    glite-ce-job-submit -a -r cream-23.pd.infn.it:8443/cream-lsf-creamtest1 test.jdl
  • the error message "Error while processing file [pippo.jdl]: Syntax error. Will not submit this JDL" should not appear anymore. In place, the message "JDL file [test.jdl] does not exist. Skipping..." should be prompted
    >glite-ce-job-submit -a -r cream-23.pd.infn.it:8443/cream-lsf-creamtest1 pippo.jdl
    2013-01-21 17:49:51,196 ERROR - JDL file [pippo.jdl] does not exist. Skipping...
    
 

Bug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

Revision 892013-01-21 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 551 to 551
 

Bug #98144 The switching off of the JobSubmissionManager makes the CREAM service not available for the users Not Implemented

Added:
>
>
  • Switch off the JobSubmissionManager in the CREAM configuration file (/etc/glite-ce-cream/cream-config.xml)
<parameter name="JOB_SUBMISSION_MANAGER_ENABLE" value="false" />

  • Restart tomcat
service tomcat5 restart

  • Submit a job by the CREAM UI.

  • Check that a message error like the following doesn't appear:
"Received NULL fault; the error is due to another cause: FaultString=[CREAM service not available: configuration failed!] - FaultCode=[SOAP-ENV:Server] - FaultSubCode=[SOAP-ENV:Server]"
 

Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

Revision 882013-01-18 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 520 to 520
 

Fixes provided with CREAM 1.14.3

Added:
>
>

Bug #99740 updateDelegationProxyInfo error: Rollback executed due to Deadlock Not Implemented

  • delegate the proxy credentials by specifying the ID of the delegated proxy
    > glite-ce-delegate-proxy -e cream-27.pd.infn.it:8443 myproxyid
  • submit ~10K long jobs to cream by forcing the submission to use the previously delegated user credentials, identified with the specified ID
    > glite-ce-job-submit --delegationId myproxyid -a -r cream-27.pd.infn.it:8443/cream-lsf-grid02 myjob.jdl
  • during the submission, at ~7000 jobs, execute in parallel several proxy renewal commands referring to the previously delegated user credentials
    > glite-ce-proxy-renew -e cream-27.pd.infn.it:8443 myproxyid
  • check the cream's logs and find the message error "updateDelegationProxyInfo error: Rollback executed due to: Deadlock found when trying to get lock; try restarting transaction": such message should not be present.

Bug #99738 Under stress conditions due to job submissions, the command queue may accumulate thousand of job purging commands Not Implemented

  • submit ~5000 very short jobs to cream and wait their terminal state (e.g. DONE-OK)
  • edit the cream's configuration file (i.e. /etc/glite-ce-cream/cream-config.xml)
  • change the JOB_PURGE_RATE parameter value to 2 minutes
    <parameter name="JOB_PURGE_RATE" value="2" /> <!-- minutes -->
  • change the JOB_PURGE_POLICY parameter value to "ABORTED 2 minutes; CANCELLED 2 minutes; DONE-OK 2 minutes; DONE-FAILED 2 minutes; REGISTERED 2 days;"
    <parameter name="JOB_PURGE_POLICY" value="ABORTED 2 minutes; CANCELLED 2 minutes; DONE-OK 2 minutes; DONE-FAILED 2 minutes; REGISTERED 2 days;" />
  • restart cream (i.e. tomcat)
    > service tomcat6 restart
  • submit further jobs to cream
  • meanwhile, during the submission, check the cream log and observe the messages about the JobPurger
  • every 2 minutes the should be logged the JobPurger activity:
JobPurger - purging 0 jobs with status REGISTERED <= Wed Jan 16 16:55:55 CET 2013
JobPurger - purging 0 jobs with status ABORTED <= Tue Jan 08 16:56:55 CET 2013
JobPurger - purging 0 jobs with status CANCELLED <= Fri Jan 18 16:51:55 CET 2013
JobPurger - purging 500 jobs with status DONE-OK <= Fri Jan 18 16:51:55 CET 2013
JobPurger - purging 0 jobs with status DONE-FAILED <= Tue Jan 08 16:56:55 CET 2013
  • access to the cream database
  • execute
    use creamdb; select * from command_queue where name="PROXY_RENEW";
    the result should be always "Empty set (0.00 sec)"

Bug #98144 The switching off of the JobSubmissionManager makes the CREAM service not available for the users Not Implemented

Bug #88134 JobWrapper doesn't handle correctly the jdl attribute “PerusalListFileURI” Not Implemented

Bug #95637 glite-ce-job-submit --help doesn't print out anything Not Implemented

Bug #95738 glite-ce-job-submit: error message to be improved if JDL file is missing Not Implemented

 

Bug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

  • in the site-info.def define the variable CE_OTHERDESCR="Cores=10.5 , Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported

Revision 872013-01-17 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1631 to 1631
 
Added:
>
>

 

CREAM Torque module

Changed:
<
<

Bug #17325 Default time limits not taken into account - Not implemented

>
>

Fixes provided with CREAM TORQUE module 2.0.1

Bug #95184 Missing real value for GlueCEPolicyMaxSlotsPerJob Not Implemented

  • configure the TORQUE server so that the parameter "resources_max.procct" for a given queue is defined and greater than zero
  • run the script /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
  • verify that the attribute GlueCEPolicyMaxSlotsPerJob for the given queue reports the value of the parameter above

Bug #96636 Time limits for GLUE 2 are different to GLUE 1 Not Implemented

  • run the command
    ldapsearch -x -H ldap://hostname:2170 -b o=glue '(&(objectclass=GLUE2ComputingShare))' [attributeName] 
    where attributeName is one of the following arguments: GLUE2ComputingShareMaxCPUTime, GLUE2ComputingShareMaxWallTime, GLUE2ComputingShareDefaultCPUTime, GLUE2ComputingShareDefaultWallTime
  • verify that each value, if available, is expressed in seconds
  • run the command
    ldapsearch -x -H ldap://hostname:2170 -b o=grid '(&(objectclass=GLUECE))' [attributeName] 
    where attributeName is one of the following arguments: GlueCEPolicyMaxCPUTime, GlueCEPolicyMaxObtainableCPUTime, GlueCEPolicyMaxWallClockTime, GlueCEPolicyMaxObtainableWallClockTime
  • verify that each value, if available, is expressed in minutes

Bug #99639 lcg-info-dynamic-scheduler-pbs cannot parse qstat output with spurious lines Not Implemented

  • save the output of the command
    qstat -f
    in a temporary file
  • insert a spurious line within the block of job data
  • run the command
    lcg-info-dynamic-scheduler-pbs -c [temporary file]
  • verify that the execution works fine

Fixes from previous releases

Bug #17325 Default time limits not taken into account - Not implemented

  To test the fix for this bug, consider a PBS installation where for a certain queue both default and max values are specified, e.g.:
Line: 1647 to 1686
 Verify that the published value for GlueCEPolicyMaxCPUTime is C and that the published value for GlueCEPolicyMaxWallClockTime is D

Changed:
<
<

Bug #49653 lcg-info-dynamic-pbs should check pcput in addition to cput - Not implemented

>
>

Bug #49653 lcg-info-dynamic-pbs should check pcput in addition to cput - Not implemented

  To test the fix for this bug, consider a PBS installation where for a certain queue both cput and pcput max values are specified, e.g.:
Line: 1670 to 1709
 Verify that the published value for GlueCEPolicyMaxCPUTime is the minimum between D and F.
Changed:
<
<

Bug #76162 YAIM for APEL parsers to use the BATCH_LOG_DIR for the batch system log location - Not implemented

>
>

Bug #76162 YAIM for APEL parsers to use the BATCH_LOG_DIR for the batch system log location - Not implemented

  To test the fix for this bug, set the yaim variable BATCH_ACCT_DIR and configure via yaim.
Line: 1688 to 1727
 Check the file /etc/glite-apel-pbs/parser-config-yaim.xml and verify that the directory name is ${TORQUE_VAR_DIR}/server_priv/accounting
Changed:
<
<

Bug #77106 PBS info provider doesn't allow - in a queue name - Not implemented

>
>

Bug #77106 PBS info provider doesn't allow - in a queue name - Not implemented

  To test the fix, configure a CREAM CE in a PBS installation where at least a queue has a - in its name.
Line: 1740 to 1793
 To test the fix, configure a CREAM CE without having also installed LSF.

yaim installation should fail saying that there were problems with LSF installation.

Deleted:
<
<
-- MassimoSgaravatto - 2011-11-07

Revision 862013-01-16 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 503 to 503
 
Deleted:
<
<

 
Deleted:
<
<

CREAM

 
Changed:
<
<

Fixes provided with CREAM 1.14.2

>
>


Fixes provided with CREAM 1.14.3

 

Bug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

Changed:
<
<
  • in the site-info.def define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0", run yaim and verify that an error is reported
>
>
  • in the site-info.def define the variable CE_OTHERDESCR="Cores=10.5 , Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=10.5"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=10.5,Benchmark=8.0", run yaim and verify that an error is reported

Bug #98440 Missing revision number in EndpointImplementationVersion Not Implemented

  • run the following command
    ldapsearch -x -H ldap://hostname:2170 -b o=glue '(&(objectclass=GLUE2Endpoint)(GLUE2EndpointImplementationName=CREAM))' GLUE2EndpointImplementationVersion
    and verify that the GLUE2EndpointImplementationVersion reports the revision number

Bug #98850 Empty ACBR list in SHARE variable Not Implemented

  • set the YAIM variable FQANVOVIEWS to "no"
  • set one the YAIM variables <QUEUE>_GROUP_ENABLE so that it contains more FQANs for the same VO (for example "atlas /atlas/ROLE=lcgadmin /atlas/ROLE=production /atlas/ROLE=pilot")
  • run the YAIM configurator and verify that in the file /etc/glite-ce-glue2/glite-ce-glue2.conf the items SHARE_<QUEUE>_<VO>_ACBRS don't contain any empty list

Bug #99072 Hard-coded reference to tomcat5.pid Not Implemented

  • on SL6 run the executable glite
    /usr/bin/glite_cream_load_monitor /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf --show
  • verify that the value of "Threshold for tomcat FD" is not zero

Bug #99085 Improve parsing of my.cnf Not Implemented

  • in the file /etc/my.cnf specify the following value
    max_connections = 256
  • runt the YAIM configurator and verify that the function config_cream_db works correctly

Bug #99282 Wrong regular expression for group.conf parsing Not Implemented

  • define YAIM variables so that one VO name is the prefix or the suffix of another one (for examples VOS=" ops dgops ")
  • run the YAIM configurator and verify that in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif no references to one VO appear as attributes of the Shares or Policies of the other

Bug #99747 glite-info-dynamic-ce does not update GLUE2ComputingShareServingState Not Implemented

  • disable the submissions to the CE
  • run the command
    /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
  • verify that the values for each "GLUE2ComputingShareServingState" are set to "draining"

Bug #99823 SHA-1 algorithm for PKCS10 generation in CREAM delegation service Not Implemented

  • insert the following line
    log4j.logger.org.glite.ce.cream.delegationmanagement.cmdexecutor=debug, fileout
    in the file /etc/glite-ce-cream/log4j.properties
  • restart tomcat
  • delegate a proxy on the CE using for the client authentication a voms-proxy whose signature algorithm is based on SHA-2, see
    openssl x509 -noout -text -in [voms-proxy]
  • verify the value reported in the log for "Signature algorithm to be used for pkcs10" is the same of the one used for the voms-proxy

Fixes provided with CREAM 1.14.2

 

Bug #95328 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

Revision 852012-12-05 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 556 to 556
 
  • open the StandardError file on the job sandbox: it should contain just the "Cannot find lb_logevent command" message.

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

Changed:
<
<
  • edit a file named test_bug94418.sh and paste on it the following text:
>
>
  • Connect to the ce under test with your pool account user
  • Edit the file /tmp/test_bug94418.sh (as your pool account user) and paste on it the following text:
 #!/bin/bash

OUTF="/tmp/sdpgu.out"

Line: 573 to 574
  wait
Changed:
<
<
  • prepare a jdl for executing the above script: example
>
>
  • On the UI prepare a jdl for executing the above script: example
 [ Type = "job"; JobType = "normal";

Revision 842012-11-20 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 540 to 540
 
  • Verify that no duplicated attributes are printed on the stdout

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Not Implemented

Changed:
<
<
  • 1) apply the patch
  • 2) access to the CREAM DB
  • 3) execute the following SQL command:
    use creamdb;
  • 4) execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;
  • 5) configure CREAM with YAIM
  • 6) repeat the steps 2, 3, 4
  • 7) check the query result at step 4: the "creationTime" value should be the same in both results while the "startUpTime" should be changed.
>
>
  • 1) access to the CREAM DB
  • 2) execute the following SQL command:
    use creamdb;
  • 3) execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;
  • 4) configure CREAM with YAIM
  • 5) repeat the steps 1, 2, 3
  • 6) check the query result at step 4: the "creationTime" value should be the same in both results while the "startUpTime" should be changed.
 

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Implemented

  • on the CREAM node, try to purge a job using the /usr/sbin/JobDBAdminPurger.sh script (none error should be reported)

Revision 832012-11-14 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 524 to 524
 
  • Configure with YAIM and run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep GLUE2EntityOtherInfo
  • Verify that the attributes defined above are reported separately
Changed:
<
<

Bug #96306 Wrong lowercase conversion for VO Tags Not Implemented

>
>

Bug #96306 Wrong lowercase conversion for VO Tags Implemented

 
  • define a tag with uppercase in the file /opt/glite/var/info/[hostname]/[vo]/[vo].list
  • run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep TESTTAG
Line: 548 to 548
 
  • 6) repeat the steps 2, 3, 4
  • 7) check the query result at step 4: the "creationTime" value should be the same in both results while the "startUpTime" should be changed.
Changed:
<
<

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Not Implemented

>
>

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Implemented

 
  • on the CREAM node, try to purge a job using the /usr/sbin/JobDBAdminPurger.sh script (none error should be reported)

Bug #97106 CREAM JW - fatal_error: command not found. Not Implemented

Revision 822012-11-14 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 10 to 10
 

Fixes provided with BLAH 1.18.2

Bug #97491 (BUpdaterLSF should not execute any bhist query if all the bhist related conf parameter are set to "no") Hard to test - Not implemented

Changed:
<
<
Fully tested by CERN: the test requires a specific CERN configuration used just by it.
>
>
  • the fix has been fully tested by CERN
  • the following is the report provided by Ulrich:
We are running this patch in production at CERN. The patch is motivated by the
fact that bhist calls are very expensive and calls to the command don't scale.
Running the command makes both the CE and the batch master unresponsive
and has therefore a severe impact on the system performance. 
While discussing the issue with the CREAM developers we found out that it
is possible to obsolete these calls and replace them with less expensive batch
system queries. For that we use the btools tool suite which provides a set
of additional LSF batch system queries which return output in machine readable
form.

Pre-requisites:
---------------
Note on btools: btools are shipped in source code with the LSF information
provider plugin. Compiling them requires LSF header files. Binaries depend on
the LSF version which is used, therefore they cannot be shipped or
automatically build due to licensing reasons.

Building Instructions:

- ensure that the LSF headers are installed on your build host

# yum install gcc rpmbuild automake autoconf info-dynamic-scheduler-lsf-btools-2.2.0-1.noarch.rpm
# cd /tmp
# tar -zxvf /usr/src/egi/btools.src.tgz
# cd btools
# ./autogen.sh
# make rpm
and install the resulting rpm

Patch version:
--------------
On EMI1 CEs (our production version) we are using a private build of the
patch glite-ce-blahp-1.16.99-0_201208291258.slc5
On EMI2 we've been testing a new build glite-ce-blahp-1.18.1-2
(Both rpms are private builds we got from Massimo Mezzadri.

Configuration of the patch
--------------------------
in /etc/blah.conf we set:

# use btools to obsolete bhist calls
bupdater_use_btools=yes
bupdater_btools_path=/usr/bin

#
bupdater_use_bhist_for_susp=no
bupdater_use_bhist_for_killed=no
bupdater_use_bhist_for_idle=no
bupdater_use_bhist_time_constraint=no
 
# CERN add caching for LSF queries
lsf_batch_caching_enabled=yes
batch_command_caching_filter=/usr/libexec/runcmd

The runcmd command is shipped with the LSF information providers. You need
at least info-dynamic-scheduler-lsf-2.2.0-1. In our configuration we cache
all batch system responses and share them using  an NFS file system. The cache
directory is a convenient way to check if any bhist calls are done by any of the
CEs by just checking for a cache file. With the above settings there are no
such calls any longer.
 

Bug #95385 (Misleading message when Cream SGE aborts jobs requesting more than one CPU) Not implemented

Line: 506 to 557
 
  • open the StandardError file on the job sandbox: it should contain just the "Cannot find lb_logevent command" message.

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

Changed:
<
<
  • Fully tested by CNAF
>
>
  • edit a file named test_bug94418.sh and paste on it the following text:
    #!/bin/bash                                                                                
                                                                                               
    OUTF="/tmp/sdpgu.out"                                                                      
                                                                                               
    MYPID=$$
    
    sleep 3600 & PID1=$!
    
    sleep 3600 & PID2=$!
    echo "MYPID=${MYPID}, PID1=${PID1}, PID2=${PID2}" > $OUTF
    echo "MYPID=${MYPID}, PID1=${PID1}, PID2=${PID2}"
    # supposedly this should kill the child processes on SIGTERM.
    trap "kill $PID1 $PID2" SIGTERM
    
    wait
    
  • prepare a jdl for executing the above script: example
    [
       Type = "job";
       JobType = "normal";
       VirtualOrganisation = "dteam";
       executable="test_bug94418.sh";
       InputSandbox = {"test_bug94418.sh"};
       InputSandboxBaseURI = "gsiftp://cream-XX.pd.infn.it/tmp"
    ]
  • submit the jdl
  • wait until the job reaches the REALLY-RUNNING state
  • check the name of the WN into which the job is running
  • on the WN, read the file /tmp/sdpgu.out which contains the PID of three processes: example
    MYPID=10551, PID1=10553, PID2=10554
  • check if all three processes exist
  • cancel the job
  • wait for its terminal state (CANCELLED)
  • check again on the WN if all three processes exist (actually they should be disappeared)
 

Bug #98707 Wrong warning message form ArgusPEPClient configuration Not Implemented

  • Run the CREAM service with default priority log level (Info)

Revision 812012-11-13 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 463 to 463
 
  • in the site-info.def define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0", run yaim and verify that an error is reported
Changed:
<
<

Bug #95382 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

>
>

Bug #95328 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

 
  • Configure a CREAM CE in cluster mode, run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GlueCE | grep InfoHostName
    and verify that one or more items exists.
Line: 508 to 508
 

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

  • Fully tested by CNAF
Changed:
<
<

Bug #93074 CREAM CE/YAIM: add knob to disable SSH key scanning. Not Implemented

  • Patch verified by the submitter.
>
>

Bug #98707 Wrong warning message form ArgusPEPClient configuration Not Implemented

  • Run the CREAM service with default priority log level (Info)
  • Perform a simple operation, for example a job list
  • Verify that in the log does not appear any warning such as "Missing or wrong argument "
 
Deleted:
<
<

Bug #78707 lcg-info-dynamic-scheduler-pbs should depend on maui-client. Not Implemented

  • Run the command
    rpm -qR lcg-info-dynamic-scheduler-pbs
    and verify that the list contains maui-client
 

Revision 802012-11-12 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Added:
>
>

Fixes provided with BLAH 1.18.2

Bug #97491 (BUpdaterLSF should not execute any bhist query if all the bhist related conf parameter are set to "no") Hard to test - Not implemented

Fully tested by CERN: the test requires a specific CERN configuration used just by it.

Bug #95385 (Misleading message when Cream SGE aborts jobs requesting more than one CPU) Not implemented

Fully tested by CERN: the test requires the CERN environment based on SGE.
 

Fixes provided with BLAH 1.18.1

Changed:
<
<

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Implemented

>
>

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Implemented

  Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.
Changed:
<
<

Bug #94519 (Updater for LSF can misidentify killed jobs as finished) implemented

>
>

Bug #94519 (Updater for LSF can misidentify killed jobs as finished) Implemented

  Verify that the value for bupdater_use_bhist_for_killed is set to yes, submit and cancel a job and verify that the status of the job reports a "jobstatus=3"
Line: 469 to 479
 
  • run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep TESTTAG
  • verify that the attributes GLUE2ApplicationEnvironmentID and GLUE2ApplicationEnvironmentAppName are uppercase.
Deleted:
<
<

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Not Implemented

  • apply the patch
  • access to the CREAM DB
  • execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;
  • configure CREAM with YAIM
  • execute again the above SQL query and check the result: the "creationTime" value should be the same in both results while the "startUpTime" should be changed

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Not Implemented

  • on the CREAM node, try to purge a job using the JobDBAdminPurger.sh script (none error should be reported)

Bug #97106 CREAM JW - fatal_error: command not found. Not Implemented

  • uninstall "glite-lb-client-progs"
  • submit a job
  • in the error file of the CREAM jobwrapper must not appear the following error: fatal_error: command not found

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

  • TODO
 

Bug #96310 Wrong lowercase conversion for Glue-1 VO Tags. Not Implemented

  • Put case-insensitive duplicated items, for example "RMON3.1 RMon3.1", in the file /opt/glite/var/info/[hostname]/[vo name]/[voname].list and file /opt/edg/var/info/[vo name]/[voname].list
  • Put a case-insensitive duplicated attributes in /var/lib/bdii/gip/ldif/static-file-Cluster.ldif, for example:
Line: 497 to 488
 
  • Run the wrapper script /var/lib/bdii/gip/plugin/glite-info-dynamic-software-wrapper
  • Verify that no duplicated attributes are printed on the stdout
Added:
>
>

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Not Implemented

  • 1) apply the patch
  • 2) access to the CREAM DB
  • 3) execute the following SQL command:
    use creamdb;
  • 4) execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;
  • 5) configure CREAM with YAIM
  • 6) repeat the steps 2, 3, 4
  • 7) check the query result at step 4: the "creationTime" value should be the same in both results while the "startUpTime" should be changed.

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Not Implemented

  • on the CREAM node, try to purge a job using the /usr/sbin/JobDBAdminPurger.sh script (none error should be reported)

Bug #97106 CREAM JW - fatal_error: command not found. Not Implemented

  • select an EMI-2 WN and uninstall the "glite-lb-client-progs" rpm in order to remove the /usr/bin/glite-lb-logevent program
  • submit several jobs to CREAM and check if at least one of them has been executed on the previously modified WN (there is no way to force to submission on a specific WN through CREAM)
  • open the StandardError file on the job sandbox: it should contain just the "Cannot find lb_logevent command" message.

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. Not Implemented

  • Fully tested by CNAF
 

Bug #93074 CREAM CE/YAIM: add knob to disable SSH key scanning. Not Implemented

  • Patch verified by the submitter.

Revision 792012-11-02 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 500 to 500
 

Bug #93074 CREAM CE/YAIM: add knob to disable SSH key scanning. Not Implemented

  • Patch verified by the submitter.
Added:
>
>

Bug #78707 lcg-info-dynamic-scheduler-pbs should depend on maui-client. Not Implemented

  • Run the command
    rpm -qR lcg-info-dynamic-scheduler-pbs
    and verify that the list contains maui-client
 

Fixes provided with CREAM 1.14.1

Revision 782012-10-12 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 488 to 488
 

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

  • TODO
Changed:
<
<

Bug #96310 Wrong lowercase conversion for Glue-1 VO Tags. TODO

  • TODO
>
>

Bug #96310 Wrong lowercase conversion for Glue-1 VO Tags. Not Implemented

  • Put case-insensitive duplicated items, for example "RMON3.1 RMon3.1", in the file /opt/glite/var/info/[hostname]/[vo name]/[voname].list and file /opt/edg/var/info/[vo name]/[voname].list
  • Put a case-insensitive duplicated attributes in /var/lib/bdii/gip/ldif/static-file-Cluster.ldif, for example:
    GlueHostApplicationSoftwareRunTimeEnvironment: MPIch
    GlueHostApplicationSoftwareRunTimeEnvironment: MPICH
    
  • Run the wrapper script /var/lib/bdii/gip/plugin/glite-info-dynamic-software-wrapper
  • Verify that no duplicated attributes are printed on the stdout
 

Bug #93074 CREAM CE/YAIM: add knob to disable SSH key scanning. Not Implemented

  • Patch verified by the submitter.

Revision 772012-10-12 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 488 to 488
 

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

  • TODO
Added:
>
>

Bug #96310 Wrong lowercase conversion for Glue-1 VO Tags. TODO

  • TODO

Bug #93074 CREAM CE/YAIM: add knob to disable SSH key scanning. Not Implemented

  • Patch verified by the submitter.
 

Fixes provided with CREAM 1.14.1

Revision 762012-09-25 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 477 to 477
 
  • configure CREAM with YAIM
  • execute again the above SQL query and check the result: the "creationTime" value should be the same in both results while the "startUpTime" should be changed
Changed:
<
<

Bug #96512 JobDBAdminPurger can't find commons-logging.jar TODO

  • TODO
>
>

Bug #96512 JobDBAdminPurger can't find commons-logging.jar Not Implemented

  • on the CREAM node, try to purge a job using the JobDBAdminPurger.sh script (none error should be reported)
 

Bug #97106 CREAM JW - fatal_error: command not found. Not Implemented

  • uninstall "glite-lb-client-progs"
Added:
>
>
  • submit a job
 
  • in the error file of the CREAM jobwrapper must not appear the following error: fatal_error: command not found

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

Revision 752012-09-25 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 480 to 480
 

Bug #96512 JobDBAdminPurger can't find commons-logging.jar TODO

  • TODO
Changed:
<
<

Bug #97106 CREAM JW - fatal_error: command not found. TODO

>
>

Bug #97106 CREAM JW - fatal_error: command not found. Not Implemented

 
  • uninstall "glite-lb-client-progs"
  • in the error file of the CREAM jobwrapper must not appear the following error: fatal_error: command not found

Revision 742012-09-25 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 481 to 481
 
  • TODO

Bug #97106 CREAM JW - fatal_error: command not found. TODO

Changed:
<
<
  • TODO
>
>
  • uninstall "glite-lb-client-progs"
  • in the error file of the CREAM jobwrapper must not appear the following error: fatal_error: command not found
 

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

  • TODO

Revision 732012-09-24 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 469 to 469
 
  • run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep TESTTAG
  • verify that the attributes GLUE2ApplicationEnvironmentID and GLUE2ApplicationEnvironmentAppName are uppercase.
Changed:
<
<

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database. TODO

  • TODO
>
>

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database Not Implemented

  • apply the patch
  • access to the CREAM DB
  • execute the following SQL query and notice the result:
    select startUpTime, creationTime from db_info;
  • configure CREAM with YAIM
  • execute again the above SQL query and check the result: the "creationTime" value should be the same in both results while the "startUpTime" should be changed
 

Bug #96512 JobDBAdminPurger can't find commons-logging.jar TODO

  • TODO
Line: 498 to 503
 

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Implemented

Changed:
<
<
Insert in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif an empty or corrupted attribute GLUE2PolicyRule (i.e. "GLUE2PolicyRule:" or "GLUE2PolicyRule: test").

Verify that in the file /etc/lrms/scheduler.conf the attribute "outputformat" is set to glue2 or both.

Run the command

/var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
and verify that no exceptions are raised.
>
>
  • Insert in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif an empty or corrupted attribute GLUE2PolicyRule (i.e. "GLUE2PolicyRule:" or "GLUE2PolicyRule: test").
  • Verify that in the file /etc/lrms/scheduler.conf the attribute "outputformat" is set to glue2 or both.
  • Run the command
    /var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
    and verify that no exceptions are raised.
 

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

Revision 722012-09-20 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 453 to 453
 
  • in the site-info.def define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0", run yaim and verify that an error is reported
Changed:
<
<

Bug #95382 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

>
>

Bug #95382 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

 
  • Configure a CREAM CE in cluster mode, run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GlueCE | grep InfoHostName
    and verify that one or more items exists.
Changed:
<
<

Bug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

>
>

Bug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

 
  • Define the YAIM variable CE_CAPABILITY="CPUScalingReferenceSI00=10 SNMPSupport=yes"
  • Configure with YAIM and run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep GLUE2EntityOtherInfo
  • Verify that the attributes defined above are reported separately
Changed:
<
<

Bug #96306 Wrong lowercase conversion for VO Tags TODO

>
>

Bug #96306 Wrong lowercase conversion for VO Tags Not Implemented

 
Changed:
<
<
  • TODO
>
>
  • define a tag with uppercase in the file /opt/glite/var/info/[hostname]/[vo]/[vo].list
  • run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep TESTTAG
  • verify that the attributes GLUE2ApplicationEnvironmentID and GLUE2ApplicationEnvironmentAppName are uppercase.
 

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database. TODO

  • TODO

Revision 712012-09-20 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 467 to 467
 
  • TODO
Added:
>
>

Bug #97441 CREAM: Unwanted auto-updating of the field "creationTime" on the creamdb database. TODO

  • TODO

Bug #96512 JobDBAdminPurger can't find commons-logging.jar TODO

  • TODO

Bug #97106 CREAM JW - fatal_error: command not found. TODO

  • TODO

Bug #94418 The SIGTERM signal should be issued to all the processes belonging to the job. TODO

  • TODO
 

Fixes provided with CREAM 1.14.1

Revision 702012-09-20 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 438 to 448
 

Fixes provided with CREAM 1.14.2

Added:
>
>

Bug #95041 YAIM could check the format of CE_OTHERDESCR Not Implemented

  • in the site-info.def define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0-HEP-SPEC06"; run yaim and verify that no error is reported
  • define the variable CE_OTHERDESCR="Cores=2,Benchmark=8.0", run yaim and verify that an error is reported

Bug #95382 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

  • Configure a CREAM CE in cluster mode, run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GlueCE | grep InfoHostName
    and verify that one or more items exists.

Bug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

  • Define the YAIM variable CE_CAPABILITY="CPUScalingReferenceSI00=10 SNMPSupport=yes"
  • Configure with YAIM and run the command
    ldapsearch -h cream-36.pd.infn.it -x -p 2170 -b "o=glue" | grep GLUE2EntityOtherInfo
  • Verify that the attributes defined above are reported separately

Bug #96306 Wrong lowercase conversion for VO Tags TODO

  • TODO
 

Fixes provided with CREAM 1.14.1

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

Revision 692012-09-20 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 436 to 436
 

CREAM

Added:
>
>

Fixes provided with CREAM 1.14.2

 

Fixes provided with CREAM 1.14.1

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

Revision 682012-09-18 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1293 to 1293
  STATUS: Implemented
Changed:
<
<
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:
>
>
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:
  • [EMI1]
 
         cream_concurrency_level="n"
Added:
>
>
  • [EMI2]
              commandworkerpoolsize="n"
    
 

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Implemented

STATUS: Implemented

Revision 672012-09-13 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 512 to 512
 

Fixes provided with CREAM 1.14

Changed:
<
<

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - Not Implemented

>
>

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - Implemented

  To verify the fix edit a VO.list file under =/opt/glite/var/info/cream-38.pd.infn.it/.list adding:

Revision 662012-08-29 - LisaZangrando

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 485 to 485
 

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

Changed:
<
<
  • create a local user having the name >14 chars size long
  • reconfigure the CE with YAIM (USE_ARGUS=no)
>
>
  • create a new local pool account having the name >14 chars size long
  • reconfigure the CE with YAIM (define USE_ARGUS=no if you don't want to configure ARGUS for handling the new local pool account)
 
  • execute any asynchronous CREAM command (e.g. jobStart, jobCancel, etc) by using the proper grid credentials which will be mapped to the new local user
  • check the CREAM log file: none message error like "Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)" should be reported

Revision 652012-08-01 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 438 to 438
 

Fixes provided with CREAM 1.14.1

Changed:
<
<

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - TBD

>
>

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

 
  • on the CREAM node, which MUST be a different machine than the one where is installed the creamdb (DB node), edit the cream-config.xml
  • find the "url" field within the datasource_creamdb element (e.g. url="jdbc:mysql://localhost:3306/creamdb?autoReconnect=true")
Line: 458 to 458
 Run the command
/var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
and verify that no exceptions are raised.

Changed:
<
<

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - TBD

>
>

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

 
  • edit the cream-config.xml and set SANDBOX_TRANSFER_METHOD="LRMS"
  • restart the cream service
Line: 483 to 483
  Example of the error:
GLUE2EndpointURL: https://cream-48.pd.infn.it8443/ce-cream/services
Changed:
<
<

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - TBD

>
>

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

 
  • create a local user having the name >14 chars size long
  • reconfigure the CE with YAIM (USE_ARGUS=no)
  • execute any asynchronous CREAM command (e.g. jobStart, jobCancel, etc) by using the proper grid credentials which will be mapped to the new local user
  • check the CREAM log file: none message error like "Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)" should be reported
Changed:
<
<

Bug #96055 Wrong DN format in logfiles for accounting - TBD

>
>

Bug #96055 Wrong DN format in logfiles for accounting - Not Implemented

 
  • submit a job and wait for success
  • verify that in the file /var/log/cream/accounting/blahp.log-yyyymmdd the value for attribute userDN is published with X500 format (i.e. "/C=../O=...)
Changed:
<
<

Bug #93091 Add some resubmission machinery to CREAM - TBD

>
>

Bug #93091 Add some resubmission machinery to CREAM - Not Implemented

 
  • edit the blah script /usr/libexec/lsf_submit.sh
  • add "sleep 10m" on the top of the script

Revision 642012-07-23 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 486 to 486
 

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - TBD

  • create a local user having the name >14 chars size long
Changed:
<
<
  • reconfigure the CE with YAIM
>
>
  • reconfigure the CE with YAIM (USE_ARGUS=no)
 
  • execute any asynchronous CREAM command (e.g. jobStart, jobCancel, etc) by using the proper grid credentials which will be mapped to the new local user
  • check the CREAM log file: none message error like "Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)" should be reported

Revision 632012-07-23 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 457 to 457
  Run the command
/var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
and verify that no exceptions are raised.
Added:
>
>
 

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - TBD

  • edit the cream-config.xml and set SANDBOX_TRANSFER_METHOD="LRMS"
Line: 1189 to 1190
 Berify that the log file is created in the specified path
Added:
>
>

Fixes provided with CREAM 1.13.4

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - see Fix for 1.14.1

 

Fixes provided with CREAM 1.13.3

Revision 622012-07-23 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 489 to 489
 
  • execute any asynchronous CREAM command (e.g. jobStart, jobCancel, etc) by using the proper grid credentials which will be mapped to the new local user
  • check the CREAM log file: none message error like "Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)" should be reported
Added:
>
>

Bug #96055 Wrong DN format in logfiles for accounting - TBD

  • submit a job and wait for success
  • verify that in the file /var/log/cream/accounting/blahp.log-yyyymmdd the value for attribute userDN is published with X500 format (i.e. "/C=../O=...)
 

Bug #93091 Add some resubmission machinery to CREAM - TBD

  • edit the blah script /usr/libexec/lsf_submit.sh

Revision 612012-07-20 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 440 to 440
 

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - TBD

Changed:
<
<
>
>
  • on the CREAM node, which MUST be a different machine than the one where is installed the creamdb (DB node), edit the cream-config.xml
  • find the "url" field within the datasource_creamdb element (e.g. url="jdbc:mysql://localhost:3306/creamdb?autoReconnect=true")
  • replace the "localhost" with the name of the remote machine (DB node) hosting the creamdb (e.g. "jdbc:mysql://cream-47.pd.infn.it:3306/creamdb?autoReconnect=true")
  • find and annotate the value of the "username" field defined in the same xml element
  • on the CREAM DB node execute the following sql commands as root (NB: sobstitute the "username" with the right value previously annotated): GRANT ALL PRIVILEGES ON creamdb.* to username@'%' IDENTIFIED BY 'username'; FLUSH PRIVILEGES;
  • on the CREAM node execute the JobDBAdminPurger.sh script (none error should be reported)
 

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Implemented

Line: 452 to 459
 

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - TBD

Changed:
<
<
>
>
  • edit the cream-config.xml and set SANDBOX_TRANSFER_METHOD="LRMS"
  • restart the cream service
  • submit the following jdl from a WMS having the URL lexicographically greater than "gsiftp://localhost" (e.g. wms01.grid.hep.ph.ic.ac.uk)
[
Type = "Job";
#VAR1 = "test1";
#VAR2 = "test2";
executable = "/bin/echo";
Arguments = "hello world!!!";
StdOutput="stdout";
StdError="stderr";
OutputSandbox = {"stdout","stderr"};
]
  • glite-wms-job-output (retrieve and check the output files)
 

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Implemented

Line: 462 to 484
 

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - TBD

Changed:
<
<
>
>
  • create a local user having the name >14 chars size long
  • reconfigure the CE with YAIM
  • execute any asynchronous CREAM command (e.g. jobStart, jobCancel, etc) by using the proper grid credentials which will be mapped to the new local user
  • check the CREAM log file: none message error like "Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)" should be reported

Bug #93091 Add some resubmission machinery to CREAM - TBD

  • edit the blah script /usr/libexec/lsf_submit.sh
  • add "sleep 10m" on the top of the script
  • submit a job
  • after 200 seconds, the following error should appears in the cream log file:
"org.glite.ce.creamapi.jobmanagement.cmdexecutor.AbstractJobExecutor - submission to BLAH failed [jobId=CREAMXXXXXXXXX; reason=BLAH error: submission command failed (exit code = 143) (stdout:) (stderr: <blah> execute_cmd: 200 seconds timeout expired, killing child process.-) N/A (jobId = CREAMXXXXXXXXX); retry count=1/3]
org.glite.ce.creamapi.jobmanagement.cmdexecutor.AbstractJobExecutor - sleeping 10 sec...
org.glite.ce.creamapi.jobmanagement.cmdexecutor.AbstractJobExecutor - sleeping 10 sec... done"
  • restore the original lsf_submit.sh script
  • after a while the job should be successufully submitted (i.e. ... JOB CREAMXXXXXXXXX STATUS CHANGED: PENDING => IDLE)
  • if you don't restore the script, the submission will be tried 3 times, then the job will abort: "JOB CREAMXXXXXXXXX STATUS CHANGED: PENDING => ABORTED [description=submission to BLAH failed [retry count=3]] [failureReason=BLAH error: submission command failed (exit code = 143) (stdout:) (stderr: execute_cmd: 200 seconds timeout expired, killing child process.-) N/A ..."
 

Fixes provided with CREAM 1.14

Revision 602012-07-19 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 469 to 469
 

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - Not Implemented

Changed:
<
<
To verify the fix edit a VO.list file under /opt/glite/var/info/cream-38.pd.infn.it/VO adding:
>
>
To verify the fix edit a VO.list file under =/opt/glite/var/info/cream-38.pd.infn.it/.list adding:
 
tag1 tag2

Revision 592012-07-18 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 9 to 9
 

Fixes provided with BLAH 1.18.1

Changed:
<
<

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Not implemented

>
>

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Implemented

  Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.

Revision 582012-07-17 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 13 to 13
  Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.
Changed:
<
<

Bug #94519 (Updater for LSF can misidentify killed jobs as finished) Not implemented

>
>

Bug #94519 (Updater for LSF can misidentify killed jobs as finished) implemented

  Verify that the value for bupdater_use_bhist_for_killed is set to yes, submit and cancel a job and verify that the status of the job reports a "jobstatus=3"

Revision 572012-07-10 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 17 to 17
  Verify that the value for bupdater_use_bhist_for_killed is set to yes, submit and cancel a job and verify that the status of the job reports a "jobstatus=3"
Changed:
<
<

Bug #94712 (Due to a timestamp problem bupdater for LSF can leave job in IDLE state) Hard to Reproduce - Not implemented

>
>

Bug #94712 (Due to a timestamp problem bupdater for LSF can leave job in IDLE state) Hard to Reproduce - Not implemented

  Not easy to reproduce (unpredictable behaviour)

Revision 562012-07-09 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 19 to 17
  Verify that the value for bupdater_use_bhist_for_killed is set to yes, submit and cancel a job and verify that the status of the job reports a "jobstatus=3"
Changed:
<
<

Bug #94712 (Due to a timestamp problem bupdater for LSF can leave job in IDLE state) Not implemented

>
>

Bug #94712 (Due to a timestamp problem bupdater for LSF can leave job in IDLE state) Hard to Reproduce - Not implemented

  Not easy to reproduce (unpredictable behaviour)
Changed:
<
<

Bug #95392 Heavy usage of 'bjobsinfo' still hurts LSF @ CERN Not implemented

>
>

Bug #95392 Heavy usage of 'bjobsinfo' still hurts LSF @ CERN Cannot be reproduced - Not implemented

  This is a cosmetic update required by CERN team; it can be reproduced only using the tools developed at CERN.
Line: 440 to 438
 

Fixes provided with CREAM 1.14.1

Changed:
<
<

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

>
>

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - TBD

 
Deleted:
<
<
TBD
 
Changed:
<
<

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Not Implemented

>
>

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Implemented

  Insert in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif an empty or corrupted attribute GLUE2PolicyRule (i.e. "GLUE2PolicyRule:" or "GLUE2PolicyRule: test").
Line: 452 to 450
  Run the command
/var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
and verify that no exceptions are raised.
Changed:
<
<

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

>
>

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - TBD

 
Deleted:
<
<
TBD
 

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Implemented

Run the command

/usr/libexec/glite-ce-glue2-endpoint-static /etc/glite-ce-glue2/glite-ce-glue2.conf | grep GLUE2EndpointURL
and verify that the URL is correctly defined (contains ":")
Changed:
<
<

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

>
>
Example of the error:
GLUE2EndpointURL: https://cream-48.pd.infn.it8443/ce-cream/services

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - TBD

 
Deleted:
<
<
TBD
 

Fixes provided with CREAM 1.14

Revision 552012-07-09 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 456 to 456
  TBD
Changed:
<
<

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Not Implemented

>
>

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Implemented

  Run the command
/usr/libexec/glite-ce-glue2-endpoint-static /etc/glite-ce-glue2/glite-ce-glue2.conf | grep GLUE2EndpointURL
and verify that the URL is correctly defined (contains ":")

Revision 542012-07-04 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Added:
>
>
 

Fixes provided with BLAH 1.18.1

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Not implemented

Line: 22 to 23
  Not easy to reproduce (unpredictable behaviour)
Added:
>
>

Bug #95392 Heavy usage of 'bjobsinfo' still hurts LSF @ CERN Not implemented

 
Added:
>
>
This is a cosmetic update required by CERN team; it can be reproduced only using the tools developed at CERN.
 

Fixes provided with BLAH 1.18.0

Line: 130 to 133
 

Bug #90082: BUpdaterPBS workaround if tracejob is in infinite loop TBD

Added:
>
>

Fixes provided with BLAH 1.16.6

See Fixes provided with BLAH 1.18.1

 

Fixes provided with BLAH 1.16.5

Bug #89527 BLAHP produced -W stage(in/out) directives are incompatible with Torque 2.5.8 Not implemented

Line: 433 to 440
 

Fixes provided with CREAM 1.14.1

Added:
>
>

Bug #89153 JobDBAdminPurger cannot purge jobs if CREAM DB is on another host - Not Implemented

TBD

 

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Not Implemented

Insert in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif an empty or corrupted attribute GLUE2PolicyRule (i.e. "GLUE2PolicyRule:" or "GLUE2PolicyRule: test").

Line: 443 to 454
 

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

Changed:
<
<
TBD
>
>
TBD
 

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Not Implemented

Line: 451 to 462
 

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

Changed:
<
<
TBD
>
>
TBD
 

Fixes provided with CREAM 1.14

Revision 532012-06-26 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 8 to 8
 

Fixes provided with BLAH 1.18.1

Changed:
<
<

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Not implemented

>
>

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Not implemented

 
Changed:
<
<
Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.
>
>
Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.
 
Line: 435 to 435
 

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Not Implemented

Changed:
<
<
TBD
>
>
Insert in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif an empty or corrupted attribute GLUE2PolicyRule (i.e. "GLUE2PolicyRule:" or "GLUE2PolicyRule: test").

Verify that in the file /etc/lrms/scheduler.conf the attribute "outputformat" is set to glue2 or both.

Run the command

/var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
and verify that no exceptions are raised.
 

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

Line: 443 to 447
 

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Not Implemented

Changed:
<
<
TBD
>
>
Run the command
/usr/libexec/glite-ce-glue2-endpoint-static /etc/glite-ce-glue2/glite-ce-glue2.conf | grep GLUE2EndpointURL
and verify that the URL is correctly defined (contains ":")
 

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

Revision 522012-06-25 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 431 to 431
 

CREAM

Added:
>
>

Fixes provided with CREAM 1.14.1

Bug #95356 Better parsing for static definition files in lcg-info-dynamic-scheduler - Not Implemented

TBD

Bug #95480 CREAM doesn't transfert the output files remotely under well known conditions - Not Implemented

TBD

Bug #95552 Malformed URL from glite-ce-glue2-endpoint-static - Not Implemented

TBD

Bug #95593 CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars - Not Implemented

TBD

 

Fixes provided with CREAM 1.14

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - Not Implemented

Revision 512012-06-14 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Added:
>
>

Fixes provided with BLAH 1.18.1

Bug #94414 (BLParserLSF could crash if a suspend on an idle job is done) Not implemented

Try to suspend a job whose status is "IDLE" and verify that the daemon BLParserLSF doesn't crash.

Bug #94519 (Updater for LSF can misidentify killed jobs as finished) Not implemented

Verify that the value for bupdater_use_bhist_for_killed is set to yes, submit and cancel a job and verify that the status of the job reports a "jobstatus=3"

Bug #94712 (Due to a timestamp problem bupdater for LSF can leave job in IDLE state) Not implemented

Not easy to reproduce (unpredictable behaviour)

 

Fixes provided with BLAH 1.18.0

Bug #84261 BNotifier on CREAM CE seems to not restart cleanly Implemented

Revision 502012-05-22 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 76 to 76
  Check the job status which eventually should be HELD.
Added:
>
>

Bug #90331 Not implemented

To test the fix submit a job, ban yourself in the ce (check here how to ban a user) and try a glite-ce-job-status. It should throw an authorization fault.
 

Bug #90927 Problem with init script for blparser Not implemented

Line: 1062 to 1064
  and configure via yaim.
Changed:
<
<
The check /etc/tomca5.conf, where there should be:
>
>
The check /etc/tomca5.conf (in EMI2 SL5 X86_64 /etc/tomcat5/tomcat5.conf), where there should be:
 
JAVA_OPTS="${JAVA_OPTS} -server -Xms512m -Xmx1024m"
Line: 1075 to 1077
  Verify that the limiter doesn't disable job submissions.
Added:
>
>
Note: to show swap partition: cat /proc/swaps to check swap: top to disable swap: swapoff -a (or swapoff /) to enable swap: swapon -a The limiter checks every 10 minutes the memory usage.
 

Bug #93768 There's a bug in logfile handling - Not Implemented

Revision 492012-05-16 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 698 to 698
 Run:
Changed:
<
<
/usr/bin/glite_cream_load_monitor --show
>
>
/usr/bin/glite_cream_load_monitor /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf --show
 

which shouldn't report any error.

Revision 482012-05-07 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 537 to 537
  and verify that the files are installed in usr/lib/python2.4 and not more in /usr/lib/python.
Added:
>
>

Bug #80295 Allow dynamic scheduler to function correctly when login shell is false - Not Implemented

To verify the fix, log on the CREAM CE as user root and run:

/sbin/runuser -s /bin/sh ldap -c "/usr/libexec/lcg-info-dynamic-scheduler -c /etc/lrms/scheduler.conf"

It should return some information in ldif format

 

Bug #80410 CREAM bulk submission CLI is desirable - Not Implemented

To test the fix, specify multiple JDLs in the glite-ce-job-submit command, e.g.:

Line: 694 to 705
 

Bug #86522 glite-ce-job-submit authorization error message difficoult to understand - Not Implemented

Changed:
<
<
TBD
>
>
To check this fix, try a submission towards a CREAM CE configured to use ARGUS when you are not authorized. You should see an error message like:

$  glite-ce-job-submit -a -r emi-demo13.cnaf.infn.it:8443/cream-lsf-demo oo.jdl
2012-05-07 20:26:51,649 FATAL - CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT not authorized for {http://www.gridsite.org/namespaces/delegation-2}getProxyReq

and not like the one reported in the savannah bug.

 

Bug #86609 yaim variable CE_OTHERDESCR not properly managed for Glue2 - Not Implemented

Line: 1028 to 1048
 
Added:
>
>

Bug #91819 glite_cream_load_monitor should read the thresholds from a conf file Implemented

Tested through the limiter test of the Robot based test-suite

Bug #92102 Tomcat attributes in the CREAM CE should be configurable via yaim - Not Implemented

Set in siteinfo.def:

CREAM_JAVA_OPTS_HEAP="-Xms512m -Xmx1024m"

and configure via yaim.

The check /etc/tomca5.conf, where there should be:

JAVA_OPTS="${JAVA_OPTS} -server -Xms512m -Xmx1024m"

Bug #92338 CREAM load limiter should not disable job submissions when there is no swap space - Not Implemented

To test the fix, consider a CREAM CE on a machine without swap.

Verify that the limiter doesn't disable job submissions.

Bug #93768 There's a bug in logfile handling - Not Implemented

To verify the fix, try the --logfile option with e.g. the glite-ce-job-submit command.

Berify that the log file is created in the specified path

 

Fixes provided with CREAM 1.13.3

Revision 462012-05-03 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 76 to 76
  Check the job status which eventually should be HELD.
Deleted:
<
<

Bug #90101 Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute may cause thread to loop TBD

 
Changed:
<
<

Bug #90927 Problem with init script for blparser TBD

>
>

Bug #90927 Problem with init script for blparser Not implemented

 
Added:
>
>
To check the fix, try to stop/start the blparser:

service glite-ce-blparser start / stop 

Then verify that the blparser has indeed been started/stopped

Bug #91318 Request to change functions in blah_common_submit_functions.sh Not implemented

Verify that in /usr/libexec/blah_common_submit_functions.sh there is this piece of code:

function bls_add_job_wrapper ()
{
  bls_start_job_wrapper >> $bls_tmp_file
  bls_finish_job_wrapper >> $bls_tmp_file
  bls_test_working_dir
}
 

Revision 452012-05-02 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 447 to 447
 
Changed:
<
<
Then re-enable the submission. Edit the script /usr/bin/glite_cream_load_monitor to trigger job submission disabling. E.g. change:
>
>
Then re-enable the submission. Edit the configuration file /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf to trigger job submission disabling. E.g. change:
 
$MemUsage  = 95;

Revision 442012-05-02 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 395 to 395
 tag3
Changed:
<
<
Then query the resource bdii, where you should see:
>
>
Wait 3 minutes and then query the resource bdii, where you should see:
 
...

Revision 432012-04-30 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 1028 to 1028
 STOP jobAdminPurger
Added:
>
>
Starting from EMI2 the command to run is:
JobDBAdminPurger.sh -c /etc/glite-ce-cream/cream-config.xml  -s DONE-FAILED,0
 

Bug #83238 Sometimes CREAM does not update the state of a failed job. - Implemented

Revision 422012-03-09 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 65 to 65
 Submit a job. In the CREAM CE the file /tmp/filewithenv should be created and it should contain the setting of some variables, including x509UserProxySubject and x509UserProxyFQAN.
Added:
>
>

Bug #90085 Suspend command doesn't work with old parser Implemented

To test the fix configure a CREAM CE with the old blparser.

Then submit a job and after a while suspend it using the glite-ce-job-suspend command.

Check the job status which eventually should be HELD.

Bug #90101 Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute may cause thread to loop TBD

Bug #90927 Problem with init script for blparser TBD

Fixes provided with BLAH 1.16.5

 

Bug #89527 BLAHP produced -W stage(in/out) directives are incompatible with Torque 2.5.8 Not implemented

To test this fix, configure a CREAM CE with PBS/Torque 2.5.8.

Line: 95 to 115
  i.e. a stagein and a stageout directives, with escaped quotes around the whole lists.
Deleted:
<
<

Bug #90085 Suspend command doesn't work with old parser Implemented

To test the fix configure a CREAM CE with the old blparser.

Then submit a job and after a while suspend it using the glite-ce-job-suspend command.

Check the job status which eventually should be HELD.

Bug #90101 Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute may cause thread to loop TBD

Bug #90927 Problem with init script for blparser TBD

 

Bug #91037 BUpdaterLSF should use bjobs to detect final job state Not implemented

To test the fix, configure a CREAM CE with LSF with the new blparser.

Line: 116 to 122
 Then edit blah.config setting:
Changed:
<
<
bupdater_debug_level=2
>
>
bupdater_debug_level=3
 

Delete the bupdater log file and restart the blparser.

Submit a job and wait for its completion and wait till then a notification with status 4 is logged in the bnotifier log file.

Changed:
<
<
grep the bupdater log file for the bhist string, which should not be found.
>
>
grep the bupdater log file for the bhist string, which should not be found, apart from something like:

2012-03-09 07:56:15 /usr/bin/BUpdaterLSF: key bupdater_use_bhist_time_constraint not found - using the default:no
2012-03-09 07:56:15 /usr/bin/BUpdaterLSF: key bupdater_use_bhist_for_killed not found - using the default:no
2012-03-09 07:56:15 /usr/bin/BUpdaterLSF: key bupdater_use_bhist_time_constraint not found - using the default:no
2012-03-09 07:56:15 /usr/bin/BUpdaterLSF: key bupdater_use_bhist_for_killed not found - using the default:no
 

Fixes provided with BLAH 1.16.4

Revision 412012-02-21 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 96 to 96
 i.e. a stagein and a stageout directives, with escaped quotes around the whole lists.
Changed:
<
<

Bug #90085 Suspend command doesn't work with old parser Not implemented

>
>

Bug #90085 Suspend command doesn't work with old parser Implemented

  To test the fix configure a CREAM CE with the old blparser.

Revision 402012-02-21 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 24 to 24
 Starting BNotifier: /opt/glite/bin/BNotifier: Error creating and binding socket: Address already in use
Changed:
<
<

Bug #86238 blahpd doesn't check the status of its daemons when idlingNot implemented

>
>

Bug #86238 blahpd doesn't check the status of its daemons when idling Implemented

  To test the fix configure a CREAM CE with the new blparser.

Revision 392012-02-19 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 557 to 557
 
Changed:
<
<

Bug #83338 endpointType (in GLUE2ServiceComplexity) hardwired to 1 in CREAM CE is not always correct - Not Implemented

>
>

Bug #83338 endpointType (in GLUE2ServiceComplexity) hardwired to 1 in CREAM CE is not always correct - Implemented

  Perform the following query on the resource bdii of the CREAM CE:

Revision 382012-02-19 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 636 to 636
  Verify that the final status is DONE-OK
Changed:
<
<

Bug #83593 Problems limiting RFC proxies in CREAM - Not Implemented

>
>

Bug #83593 Problems limiting RFC proxies in CREAM - Implemented

  Consider the same test done for bug #83592
Line: 893 to 894
 Try also a job submission to verify if everything works properly.
Changed:
<
<

Bug #89489 yaim plugin for CREAM CE does not execute a check function due to name mismatch - Not Implemented

>
>

Bug #89489 yaim plugin for CREAM CE does not execute a check function due to name mismatch - Implemented

  Configure a CREAM CE via yaim and save the yaim output. It should contain the string:

Revision 372012-02-19 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 613 to 613
 
Changed:
<
<

Bug #83592 CREAM client doesn't allow the delegation of RFC proxies - Not Implemented

>
>

Bug #83592 CREAM client doesn't allow the delegation of RFC proxies - Implemented

  Create a RFC proxy, e.g.:

Revision 362012-02-17 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 8 to 8
 

Fixes provided with BLAH 1.18.0

Changed:
<
<

Bug #84261 BNotifier on CREAM CE seems to not restart cleanly Not implemented

>
>

Bug #84261 BNotifier on CREAM CE seems to not restart cleanly Implemented

  To test the fix, configure a CREAM CE using the new blparser.

Revision 352012-02-07 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 65 to 65
 Submit a job. In the CREAM CE the file /tmp/filewithenv should be created and it should contain the setting of some variables, including x509UserProxySubject and x509UserProxyFQAN.
Deleted:
<
<

Bug #89504 Repeated notification problem for BLParserLSF TBD

 

Bug #89527 BLAHP produced -W stage(in/out) directives are incompatible with Torque 2.5.8 Not implemented

To test this fix, configure a CREAM CE with PBS/Torque 2.5.8.

Line: 98 to 96
 i.e. a stagein and a stageout directives, with escaped quotes around the whole lists.
Deleted:
<
<

Bug #90082 BUpdaterPBS workaround if tracejob is in infinite loop TBD

 

Bug #90085 Suspend command doesn't work with old parser Not implemented

To test the fix configure a CREAM CE with the old blparser.

Revision 342012-02-07 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 36 to 36
 
Changed:
<
<

Bug #86918 Request for passing all submit command attributes to the local configuration script. TBD

>
>

Bug #86918 Request for passing all submit command attributes to the local configuration script. Not implemented

To test this fix, create/edit the /usr/libexec/pbs_local_submit_attributes.sh (for PBS) script adding:

export gridType x509UserProxyFQAN uniquejobid queue ceid VirtualOrganisation ClientJobId x509UserProxySubject
env > /tmp/filewithenv

Edit the /etc/blah,config file adding:

blah_pass_all_submit_attributes=yes

Submit a job. In the CREAM CE the file /tmp/filewithenv should be created and it should contain the setting of some variables, including the ones exported in the /usr/libexec/pbs_local_submit_attributes.sh script.

Then edit the /etc/blah,config file, removing the previously added line, and adding:

blah_pass_submit_attributes[0]="x509UserProxySubject"
blah_pass_submit_attributes[1]="x509UserProxyFQAN"

Submit a job. In the CREAM CE the file /tmp/filewithenv should be created and it should contain the setting of some variables, including x509UserProxySubject and x509UserProxyFQAN.

 

Bug #89504 Repeated notification problem for BLParserLSF TBD

Revision 332012-02-06 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 8 to 8
 

Fixes provided with BLAH 1.18.0

Added:
>
>

Bug #84261 BNotifier on CREAM CE seems to not restart cleanly Not implemented

To test the fix, configure a CREAM CE using the new blparser.

Then try a:

service gLite restart

It shouldn't report the error message:

Starting BNotifier: /opt/glite/bin/BNotifier: Error creating and binding socket: Address already in use
 

Bug #86238 blahpd doesn't check the status of its daemons when idlingNot implemented

To test the fix configure a CREAM CE with the new blparser.

Revision 322012-02-02 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 70 to 70
 

Bug #90927 Problem with init script for blparser TBD

Added:
>
>

Bug #91037 BUpdaterLSF should use bjobs to detect final job state Not implemented

To test the fix, configure a CREAM CE with LSF with the new blparser.

Then edit blah.config setting:

 bupdater_debug_level=2

Delete the bupdater log file and restart the blparser.

Submit a job and wait for its completion and wait till then a notification with status 4 is logged in the bnotifier log file.

grep the bupdater log file for the bhist string, which should not be found.

 

Fixes provided with BLAH 1.16.4

Bug #88974 BUpdaterSGE and BNotifier don't start if sge_helperpath var is not fixed Not implemented

Revision 312012-01-31 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 8 to 8
 

Fixes provided with BLAH 1.18.0

Changed:
<
<

Bug #86238 blahpd doesn't check the status of its daemons when idlingTBD

>
>

Bug #86238 blahpd doesn't check the status of its daemons when idlingNot implemented

To test the fix configure a CREAM CE with the new blparser.

Don't use it (i.e. do not submit jobs nor issue any other commands).

kill the budater and bnotifier processes.

Wait for 1 minute: you should see that the bupdater and bnotifier have been restarted.

 

Bug #86918 Request for passing all submit command attributes to the local configuration script. TBD

Revision 302012-01-31 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 45 to 45
 i.e. a stagein and a stageout directives, with escaped quotes around the whole lists.
Added:
>
>

Bug #90082 BUpdaterPBS workaround if tracejob is in infinite loop TBD

Bug #90085 Suspend command doesn't work with old parser Not implemented

To test the fix configure a CREAM CE with the old blparser.

Then submit a job and after a while suspend it using the glite-ce-job-suspend command.

Check the job status which eventually should be HELD.

Bug #90101 Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute may cause thread to loop TBD

Bug #90927 Problem with init script for blparser TBD

 

Fixes provided with BLAH 1.16.4

Revision 292012-01-31 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Added:
>
>

Fixes provided with BLAH 1.18.0

Bug #86238 blahpd doesn't check the status of its daemons when idlingTBD

Bug #86918 Request for passing all submit command attributes to the local configuration script. TBD

Bug #89504 Repeated notification problem for BLParserLSF TBD

Bug #89527 BLAHP produced -W stage(in/out) directives are incompatible with Torque 2.5.8 Not implemented

To test this fix, configure a CREAM CE with PBS/Torque 2.5.8.

If this is not possible and you have another torque version, apply the change documented at:

https://wiki.italiangrid.it/twiki/bin/view/CREAM/TroubleshootingGuide#5_1_Saving_the_batch_job_submiss

to save the submission script.

Submit a job and check in /tmp the pbs job submission script.

It should contain something like:

#PBS -W stagein=\'CREAM610186385_jobWrapper.sh.18757.13699.1328001723@cream-38.pd.infn.it:/var/c\
ream_sandbox/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role\
_NULL_Capability_NULL_dteam042/61/CREAM610186385/CREAM610186385_jobWrapper.sh,cre38_610186385.pr\
oxy@cream-38.pd.infn.it:/var/cream_sandbox/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Cert\
ificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/proxy/5a34c64e2a8db2569284306e9a472\
3d2d40045a7_13647008746533\'
#PBS -W stageout=\'out_cre38_610186385_StandardOutput@cream-38.pd.infn.it:/var/cream_sandbox/dte\
am/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability\
_NULL_dteam042/61/CREAM610186385/StandardOutput,err_cre38_610186385_StandardError@cream-38.pd.in\
fn.it:/var/cream_sandbox/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_I\
T_dteam_Role_NULL_Capability_NULL_dteam042/61/CREAM610186385/StandardError\'

i.e. a stagein and a stageout directives, with escaped quotes around the whole lists.

 

Fixes provided with BLAH 1.16.4

Bug #88974 BUpdaterSGE and BNotifier don't start if sge_helperpath var is not fixed Not implemented

Revision 282012-01-19 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 160 to 160
 
Changed:
<
<

Bug #81824 (yaim-cream-ce should manage the attribute bupdater_loop_interval) Not implemented

>
>

Bug #81824 (yaim-cream-ce should manage the attribute bupdater_loop_interval) Implemented

  Set BUPDATER_LOOP_INTERVAL to 30 in siteinfo.def and reconfigure via yaim. Then verify that in blah.config there is:
Line: 971 to 971
 

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Implemented

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix, submit the following JDL using glite-ce-job-submit:

Revision 272012-01-18 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 969 to 969
  cream_concurrency_level="n"
Changed:
<
<

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Not implemented

>
>

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Implemented

  STATUS: Not implemented

Revision 262012-01-18 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 315 to 315
 
Added:
>
>
Then re-enable the submission. Edit the script /usr/bin/glite_cream_load_monitor to trigger job submission disabling. E.g. change:

$MemUsage  = 95;

with:

$MemUsage  = 1;

Wait 15 minutes and then perform the following ldap query:

# ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=grid" | grep GlueCEStateStatus

For each GlueCE this should return:

GlueCEStateStatus: Draining
 

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

STATUS: Implemented

Revision 252012-01-18 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 885 to 885
  FailureReason = [Job has been terminated (got SIGTERM)]
Changed:
<
<

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Not implemented

>
>

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Implemented

  STATUS: Not implemented

Revision 242012-01-17 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 391 to 391
  Then move the conf file as ~/.glite/VO/glite_cream.conf and repeat the test which should give the same result
Changed:
<
<

Bug #82206 yaim-cream-ce: BATCH_LOG_DIR missing among the required attributes - Not Implemented TBD

>
>

Bug #82206 yaim-cream-ce: BATCH_LOG_DIR missing among the required attributes - Not Implemented

  Try to configure a CREAM CE with Torque using yaim without setting BLPARSER_WITH_UPDATER_NOTIFIER and without setting BATCH_LOG_DIR.
Changed:
<
<
It should fail saying: xxx
>
>
It should fail saying:
 
Added:
>
>
 INFO: Executing function: config_cream_blah_check 
 ERROR: BATCH_LOG_DIR is not set
 ERROR: Error during the execution of function: config_cream_blah_check
 

Bug #83314 Information about the RTEpublisher service should be available also in glue2 - Not Implemented

Line: 612 to 616
 
Changed:
<
<

Bug #86737 A different port number than 9909 should be used for CREAM_JOB_SENSOR - Not Implemented TBD

>
>

Bug #86737 A different port number than 9909 should be used for CREAM_JOB_SENSOR - Not Implemented

On a running CREAM CE, perform the following command:

netstat -an | grep -i 9909

This shouldn't return anything.

 

Bug #86773 wrong /etc/glite-ce-cream/cream-config.xml with multiple ARGUS servers set - Not Implemented

Revision 232012-01-13 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 643 to 643
 
Added:
>
>

Bug #87690 Not possible to map different queues to different clusters for CREAM configured in cluster mode - Not Implemented

Configure via yaim a CREAM CE in cluster mode with different queues mapped to different clusters, e.g.:

CREAM_CLUSTER_MODE=yes
CE_HOST_cream_47_pd_infn_it_QUEUES="creamtest1 creamtest2"
QUEUE_CREAMTEST1_CLUSTER_UniqueID=cl1id
QUEUE_CREAMTEST2_CLUSTER_UniqueID=cl2id

Then query the resource bdii of the CREAM, and check the GlueForeignKey attributes of the different glueCEs: they should refer to the specified clusters:

ldapsearch -h cream-47.pd.infn.it -p 2170 -x -b o=grid objectclass=GlueCE GlueForeignKey
# extended LDIF
#
# LDAPv3
# base <o=grid> with scope subtree
# filter: objectclass=GlueCE
# requesting: GlueForeignKey 
#

# cream-47.pd.infn.it:8443/cream-lsf-creamtest2, resource, grid
dn: GlueCEUniqueID=cream-47.pd.infn.it:8443/cream-lsf-creamtest2,Mds-Vo-name=r
 esource,o=grid
GlueForeignKey: GlueClusterUniqueID=cl12d

# cream-47.pd.infn.it:8443/cream-lsf-creamtest1, resource, grid
dn: GlueCEUniqueID=cream-47.pd.infn.it:8443/cream-lsf-creamtest1,Mds-Vo-name=r
 esource,o=grid
GlueForeignKey: GlueClusterUniqueID=cl1id

Bug #87799 Add yaim variables to configure the GLUE 2 WorkingArea attributes - Not Implemented

Set all (or some) of the following yaim variables:

WORKING_AREA_SHARED
WORKING_AREA_GUARANTEED
WORKING_AREA_TOTAL
WORKING_AREA_FREE
WORKING_AREA_LIFETIME
WORKING_AREA_MULTISLOT_TOTAL
WORKING_AREA_MULTISLOT_FREE
WORKING_AREA_MULTISLOT_LIFETIME

and then configure via yaim. Then query the resource bdii of the CREAM CE and verify that the relevant attributes of the glue2 ComputingManager object are set.

Bug #88078 CREAM DB names should be configurable - Not Implemented

Configure from scratch a CREAM CE setting the yaim variables: CREAM_DB_NAME and DELEGATION_DB_NAME, e.g.:

CREAM_DB_NAME=abc
DELEGATION_DB_NAME=xyz

and then configure via yaim.

Then check if the two databases have been created:

# mysql -u xxx -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7176 Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show databases;

+--------------------+

Database
+--------------------+
information_schema
abc
test
xyz
+--------------------+ 4 rows in set (0.02 sec)

Try also a job submission to verify if everything works properly.

Bug #89489 yaim plugin for CREAM CE does not execute a check function due to name mismatch - Not Implemented

Configure a CREAM CE via yaim and save the yaim output. It should contain the string:

INFO: Executing function: config_cream_gip_scheduler_plugin_check

Bug #89664 yaim-cream-ce doesn't manage spaces in CE_OTHERDESCR - Not Implemented

Try to set the yaim variable CE_OTHERDESCR to:

CE_OTHERDESCR="Cores=1"

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=1

Try then to set the yaim variable CE_OTHERDESCR to:

CE_OTHERDESCR="Cores=2, Benchmark=4-HEP-SPEC06"

and reconfigure via yaim.

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=2

Then perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=Glue2Benchmark 

This should return something like:

# cream-47.pd.infn.it_hep-spec06, cream-47.pd.infn.it, ppp, resource, glue
dn: GLUE2BenchmarkID=cream-47.pd.infn.it_hep-spec06,GLUE2ResourceID=cream-47.pd.infn.it,GLUE2ServiceID=ppp,GLUE2GroupID=resource,o=glue
GLUE2BenchmarkExecutionEnvironmentForeignKey: cream-47.pd.infn.it
GLUE2BenchmarkID: cream-47.pd.infn.it_hep-spec06
GLUE2BenchmarkType: hep-spec06
objectClass: GLUE2Entity
objectClass: GLUE2Benchmark
GLUE2EntityCreationTime: 2012-01-13T17:07:52Z
GLUE2BenchmarkValue: 4
GLUE2EntityOtherInfo: InfoProviderName=glite-ce-glue2-benchmark-static
GLUE2EntityOtherInfo: InfoProviderVersion=1.0
GLUE2EntityOtherInfo: InfoProviderHost=cream-47.pd.infn.it
GLUE2BenchmarkComputingManagerForeignKey: ppp_Manager
GLUE2EntityName: Benchmark hep-spec06

Bug #89784 Improve client side description of authorization failure - Not Implemented

Try to remove the lsc files for your VO and try a submission to that CE.

It should return an authorization error.

Then check the glite-ce-cream.log. It should report something like:

13 Jan 2012 18:21:21,270 org.glite.voms.PKIVerifier - Cannot find usable certificates to validate the AC. Check that the voms server host certificate is in your vomsdir directory.
13 Jan 2012 18:21:21,602 org.glite.ce.commonj.authz.gjaf.LocalUserPIP - glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
13 Jan 2012 18:21:21,603 org.glite.ce.commonj.authz.gjaf.ServiceAuthorizationChain - Failed to get the local user id via glexec: glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
org.glite.ce.commonj.authz.AuthorizationException: Failed to get the local user id via glexec: glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
 

Fixes provided with CREAM 1.13.3

Revision 222012-01-13 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 554 to 554
 ldapsearch -h -x -p 2170 -b "o=glue" objectclass=Glue2Benchmark
Changed:
<
<
xxx
>
>
This should return something like:

dn: GLUE2BenchmarkID=cream-47.pd.infn.it_hep-spec06,GLUE2ResourceID=cream-47.pd.infn.it,GLUE2ServiceID=cream-47.pd.infn.it_ComputingElement,GLUE2GroupID=re
 source,o=glue
GLUE2BenchmarkExecutionEnvironmentForeignKey: cream-47.pd.infn.it
GLUE2BenchmarkID: cream-47.pd.infn.it_hep-spec06
GLUE2BenchmarkType: hep-spec06
objectClass: GLUE2Entity
objectClass: GLUE2Benchmark
GLUE2EntityCreationTime: 2012-01-13T14:04:48Z
GLUE2BenchmarkValue: 150
GLUE2EntityOtherInfo: InfoProviderName=glite-ce-glue2-benchmark-static
GLUE2EntityOtherInfo: InfoProviderVersion=1.0
GLUE2EntityOtherInfo: InfoProviderHost=cream-47.pd.infn.it
GLUE2BenchmarkComputingManagerForeignKey: cream-47.pd.infn.it_ComputingElement_Manager
GLUE2EntityName: Benchmark hep-spec06

Bug #86694 A different port number than 9091 should be used for LRMS_EVENT_LISTENER - Not Implemented

On a running CREAM CE, perform the following command:

netstat -an | grep -i 9091

This shouldn't return anything.

Then perform the following command:

netstat -an | grep -i 49152

This should return:

tcp        0      0 :::49152                    :::*                        LISTEN      

[root@cream-47 ~]# netstat -an | grep -i 49153 [root@cream-47 ~]# netstat -an | grep -i 49154 [root@cream-47 ~]# netstat -an | grep -i 9091

Bug #86697 User application's exit code not recorded in the CREAM log file - Not Implemented

Submit a job and wait for its completion. Then check the glite-ce-cream.log file on the CREAM CE. The user exit code should be reported (filed exitCode), e.g.:

13 Jan 2012 15:22:52,966 org.glite.ce.creamapi.jobmanagement.cmdexecutor.AbstractJobExecutor - JOB CREAM124031222 STATUS CHANGED: REALLY-RUNNING => DONE-OK [failureReason=reason=0] [exitCode=23] [localUser=dteam004] [workerNode=prod-wn-001.pn.pd.infn.it] [delegationId=7a52772caaeea96628a1ff9223e67a1f6c6dde9f]

Bug #86737 A different port number than 9909 should be used for CREAM_JOB_SENSOR - Not Implemented TBD

Bug #86773 wrong /etc/glite-ce-cream/cream-config.xml with multiple ARGUS servers set - Not Implemented

To test the fix, set in the siteinfo,def:

USE_ARGUS=yes
ARGUS_PEPD_ENDPOINTS="https://cream-46.pd.infn.it:8154/authz https://cream-46-1.pd.infn.it:8154/authz"
CREAM_PEPC_RESOURCEID="http://pd.infn.it/cream-47"

i.e. 2 values for ARGUS_PEPD_ENDPOINTS.

Then configure via yaim.

In /etc/glite-ce-cream/cream-config.xml there should be:

 <argus-pep name="pep-client1"
             resource_id="http://pd.infn.it/cream-47"
             cert="/etc/grid-security/tomcat-cert.pem"
             key="/etc/grid-security/tomcat-key.pem"
             passwd=""
             mapping_class="org.glite.ce.cream.authz.argus.ActionMapping">
    <endpoint url="https://cream-46.pd.infn.it:8154/authz" />
    <endpoint url="https://cream-46-1.pd.infn.it:8154/authz" />
  </argus-pep>
 

Fixes provided with CREAM 1.13.3

Revision 212012-01-13 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 353 to 353
  and verify that the files are installed in usr/lib/python2.4 and not more in /usr/lib/python.
Changed:
<
<

Bug #80410 CREAM bulk submission CLI is desirable TBD

>
>

Bug #80410 CREAM bulk submission CLI is desirable - Not Implemented

 
Changed:
<
<

Bug #81734 removed conf file retrieve from old path that is not EMI compliant TBD

>
>
To test the fix, specify multiple JDLs in the glite-ce-job-submit command, e.g.:

glite-ce-job-submit --debug -a -r cream-47.pd.infn.it:8443/cream-lsf-creamtest1 jdl1.jdl jdl2.jdl jdl3.jdl

Considering the above example, verify that 3 jobs are submitted and 3 jobids are returned.

Bug #81734 removed conf file retrieve from old path that is not EMI compliant - Not Implemented

To test the fix, create the conf file /etc/glite_cream.conf with the following content:

[
CREAM_URL_PREFIX="abc://";
]

Try then e.g. the following command:

glite-ce-job-list --debug cream-47.pd.infn.it

It should report that it is trying to contact abc://cream-47.pd.infn.it:8443//ce-cream/services/CREAM2:

2012-01-13 14:44:39,028 DEBUG - Service address=[abc://cream-47.pd.infn.it:8443//ce-cream/services/CREAM2]

Move the conf file as /etc/VO/glite_cream.conf and repeat the test which should give the same result

Then move the conf file as ~/.glite/VO/glite_cream.conf and repeat the test which should give the same result

 

Bug #82206 yaim-cream-ce: BATCH_LOG_DIR missing among the required attributes - Not Implemented TBD

Line: 365 to 399
 
Changed:
<
<

Bug #83314 Information about the RTEpublisher service should be available also in glue2 - Not Implemented TBD

>
>

Bug #83314 Information about the RTEpublisher service should be available also in glue2 - Not Implemented

  Check if the resource BDII publishes glue 2 GLUE2ComputingEndPoint objectclasses with GLUE2EndpointInterfaceName equal to org.glite.ce.ApplicationPublisher. If the CE is configured in no cluster mode there should be one of such objectclass. If the CE is configured in cluster mode and the gLite-CLUSTER is deployed on a different node, there shouldn't be any of such objectclasses.
Line: 494 to 528
 

Try then to set the yaim variable CE_OTHERDESCR to:

Deleted:
<
<
xxxx
 
Added:
>
>
CE_OTHERDESCR="Cores=1,Benchmark=150-HEP-SPEC06

and reconfigure via yaim.

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=1

Then perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=Glue2Benchmark 

xxx

 

Fixes provided with CREAM 1.13.3

Revision 202012-01-12 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 364 to 364
 It should fail saying: xxx
Added:
>
>

Bug #83314 Information about the RTEpublisher service should be available also in glue2 - Not Implemented TBD

Check if the resource BDII publishes glue 2 GLUE2ComputingEndPoint objectclasses with GLUE2EndpointInterfaceName equal to org.glite.ce.ApplicationPublisher. If the CE is configured in no cluster mode there should be one of such objectclass. If the CE is configured in cluster mode and the gLite-CLUSTER is deployed on a different node, there shouldn't be any of such objectclasses.

ldapsearch -h  <CREAM CE hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"

Bug #83338 endpointType (in GLUE2ServiceComplexity) hardwired to 1 in CREAM CE is not always correct - Not Implemented

Perform the following query on the resource bdii of the CREAM CE:

 -p 2170 -b "o=glue" | grep -i endpointtype

endpointtype should be 3 if CEMon is deployed (USE_CEMON is true). 2 otherwise.

Bug #83474 Some problems concerning glue2 publications of CREAM CE configured in cluster mode - Not Implemented

Configure a CREAM CE in cluster mode, with the gLite-CLUSTER configured on a different host.

ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingService

ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.CREAM))"

  • Check if the resource BDII publishes glue 2 GLUE2Manager objectclasses. There shouldn't be any GLUE2Manager objectclass.

ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Manager

  • Check if the resource BDII publishes glue 2 GLUE2Share objectclasses. There shouldn't be any GLUE2Share objectclass.

ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Share

ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment

ldapsearch -h  <CREAM CE hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"

Bug #83592 CREAM client doesn't allow the delegation of RFC proxies - Not Implemented

Create a RFC proxy, e.g.:

voms-proxy-init -voms dteam -rfc

and then submit using glite-ce-job-submit a job using ISB and OSB, e.g.:

[
executable="ssh1.sh";
inputsandbox={"file:///home/sgaravat/JDLExamples/ssh1.sh", "file:///home/sgaravat/a"};
stdoutput="out3.out";
stderror="err2.err";
outputsandbox={"out3.out", "err2.err", "ssh1.sh", "a"};
outputsandboxbasedesturi="gsiftp://localhost";
]

Verify that the final status is DONE-OK

Bug #83593 Problems limiting RFC proxies in CREAM - Not Implemented

Consider the same test done for bug #83592

Bug #84308 Error on glite_cream_load_monitor if cream db is on another host - Not Implemented

Configure a CREAM CE with the database installed on a different host than the CREAM CE.

Run:

/usr/bin/glite_cream_load_monitor --show

which shouldn't report any error.

Bug #86522 glite-ce-job-submit authorization error message difficoult to understand - Not Implemented

TBD

Bug #86609 yaim variable CE_OTHERDESCR not properly managed for Glue2 - Not Implemented

Try to set the yaim variable CE_OTHERDESCR to:

CE_OTHERDESCR="Cores=1"

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=1

Try then to set the yaim variable CE_OTHERDESCR to: xxxx

 

Fixes provided with CREAM 1.13.3

Revision 192012-01-12 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 342 to 342
  ERROR: sudo probably not installed !
Added:
>
>

Bug #79362 location of python files provided with lcg-info-dynamic-scheduler-generic-2.3.5-0.sl5 - Not Implemented

To verify the fix, do a:

rpm -ql dynsched-generic

and verify that the files are installed in usr/lib/python2.4 and not more in /usr/lib/python.

Bug #80410 CREAM bulk submission CLI is desirable TBD

Bug #81734 removed conf file retrieve from old path that is not EMI compliant TBD

Bug #82206 yaim-cream-ce: BATCH_LOG_DIR missing among the required attributes - Not Implemented TBD

Try to configure a CREAM CE with Torque using yaim without setting BLPARSER_WITH_UPDATER_NOTIFIER and without setting BATCH_LOG_DIR.

It should fail saying: xxx

 

Fixes provided with CREAM 1.13.3

Revision 182012-01-09 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 6 to 6
 

BLAH

Changed:
<
<

Bug #75854 Problems related to the growth of the blah registry) Not implemented

>
>

Fixes provided with BLAH 1.16.4

Bug #88974 BUpdaterSGE and BNotifier don't start if sge_helperpath var is not fixed Not implemented

Install and configure (via yaim) a CREAM-CE using GE as batch system.

Make sure that in /etc/blah.config the variable sge_helperpath is commented/is not there.

Try to restart the blparser: /etc/init.d/glite-ce-blahparser restart

It should work without problems. In particular it should not report the following error:

Starting BNotifier: /usr/bin/BNotifier: sge_helperpath not defined. Exiting
[FAILED]
Starting BUpdaterSGE: /usr/bin/BUpdaterSGE: sge_helperpath not defined. Exiting
[FAILED] 

Bug 89859 There is a memory leak in the updater for LSF, PBS and Condor Not implemented

Configure a CREAM CE using the new blparser.

Submit 1000 jobs using e.g. this JDL:

[
executable="/bin/sleep";
arguments="100";
]

Keep monitoring the memory used by the bupdaterxxx process. It should basically not increase.

The test should be done for both LSF and Torque/PBS.

Fixes provided with BLAH 1.16.3

Bug #75854 Problems related to the growth of the blah registry) Not implemented

  Configure a CREAM CE using the new BLparser.
Line: 23 to 61
  Monitor the BLAH processed. Verify that each of them doesn't use more than 50 MB.
Changed:
<
<

Bug #77776 (BUpdater should have an option to use cached batch system commands) Not implemented

>
>

Bug #77776 (BUpdater should have an option to use cached batch system commands) Not implemented

  Add:
Line: 65 to 103
 
Changed:
<
<

Bug #80805 (BLAH job registry permissions should be improved) Not implemented

>
>

Bug #80805 (BLAH job registry permissions should be improved) Not implemented

  Check permissions and ownership under /var/blah. They should be:
Line: 91 to 129
 /var/blah/user_blah_job_registry.bjr/registry.proxydir: total 0
Changed:
<
<

Bug #81354 (Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute causes thread to loop) Not implemented

>
>

Bug #81354 (Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute causes thread to loop) Not implemented

  Log on a cream ce as user tomcat. Create a proxy of yours and copy it as /tmp/proxy (change the ownership to tomcat.tomcat).
Line: 121 to 160
 
Changed:
<
<

Bug #81824 (yaim-cream-ce should manage the attribute bupdater_loop_interval) Not implemented

>
>

Bug #81824 (yaim-cream-ce should manage the attribute bupdater_loop_interval) Not implemented

  Set BUPDATER_LOOP_INTERVAL to 30 in siteinfo.def and reconfigure via yaim. Then verify that in blah.config there is:
Line: 129 to 168
 bupdater_loop_interval=30
Changed:
<
<

Bug #82281 (blahp.log records should always contain CREAM job ID) Not implement

>
>

Bug #82281 (blahp.log records should always contain CREAM job ID) Not implement

 

Submit a job directly to CREAM using CREAM-CLI.

Line: 144 to 183
 
Changed:
<
<

Bug #82297 (blahp.log rotation period is too short) Not implemented

>
>

Bug #82297 (blahp.log rotation period is too short) Not implemented

  Check that in /etc/logrotate.d/blahp-logrotate rotate is equal to 365:
Line: 160 to 199
 
Changed:
<
<

Bug #83275 (Problem in updater with very short jobs that can cause no notification to cream) Not implemented

>
>

Bug #83275 (Problem in updater with very short jobs that can cause no notification to cream) Not implemented

  Configure a CREAM CE using the new blparser. Submit a job using the following JDL:
Line: 178 to 217
 2011-11-04 14:11:11 Sent for Cream:[BatchJobId="927.cream-38.pd.infn.it"; JobStatus=4; ChangeTime="2011-11-04 14:08:55"; JwExitCode=0; Reason="reason=0"; ClientJobId="622028514"; BlahJobName="cre38_622028514";]
Changed:
<
<

Bug #83347 (Incorrect special character handling for BLAH Arguments and Environment attributes) Not implemented

>
>

Bug #83347 (Incorrect special character handling for BLAH Arguments and Environment attributes) Not implemented

  Log on a cream ce as user tomcat. Create a proxy of yours and copy it as /tmp/proxy (change the ownership to tomcat.tomcat).
Line: 196 to 235
 
Changed:
<
<

Bug #87419 (blparser_master add some spurious character in the BLParser command line) Not implemented

>
>

Bug #87419 (blparser_master add some spurious character in the BLParser command line) Not implemented

  Configure a CREAM CE using the old blparser. Check the blparser process using ps. It shouldn't show urious characters:
Line: 206 to 245
 
Deleted:
<
<

Bug #88974 BUpdaterSGE and BNotifier don't start if sge_helperpath var is not fixed Not implemented

 
Deleted:
<
<
Install and configure (via yaim) a CREAM-CE using GE as batch system.
 
Deleted:
<
<
Make sure that in /etc/blah.config the variable sge_helperpath is commented/is not there.
 
Changed:
<
<
Try to restart the blparser: /etc/init.d/glite-ce-blahparser restart
>
>

 
Changed:
<
<
It should work without problems. In particular it should not report the following error:
>
>

CREAM

Fixes provided with CREAM 1.14

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - Not Implemented

To verify the fix edit a VO.list file under /opt/glite/var/info/cream-38.pd.infn.it/VO adding:

 
Changed:
<
<
Starting BNotifier: /usr/bin/BNotifier: sge_helperpath not defined. Exiting [FAILED] Starting BUpdaterSGE: /usr/bin/BUpdaterSGE: sge_helperpath not defined. Exiting [FAILED]
>
>
tag1 tag2 tag3
 
Changed:
<
<

Bug 89859 There is a memory leak in the updater for LSF, PBS and Condor Not implemented

>
>
Then query the resource bdii, where you should see:
 
Changed:
<
<
Configure a CREAM CE using the new blparser.
>
>
...
GlueHostApplicationSoftwareRunTimeEnvironment: tag1
GlueHostApplicationSoftwareRunTimeEnvironment: tag2
GlueHostApplicationSoftwareRunTimeEnvironment: tag3
...
 
Changed:
<
<
Submit 1000 jobs using e.g. this JDL:
>
>

Bug #68968 lcg-info-dynamic-software should protect against duplicate RTE tags - Not Implemented

To verify the fix edit a VO.list file under /opt/glite/var/info/cream-38.pd.infn.it/VO adding:

 
Changed:
<
<
[ executable="/bin/sleep"; arguments="100"; ]
>
>
tag1 tag2 TAG1 tag1
 
Changed:
<
<
Keep monitoring the memory used by the bupdaterxxx process. It should basically not increase.
>
>
Then query the resource bdii:
 
Changed:
<
<
The test should be done for both LSF and Torque/PBS.
>
>
ldapsearch -h <CE host> -x -p 2170 -b "o=grid" | grep -i tag
 
Added:
>
>
This should return:
 
Changed:
<
<

>
>
GlueHostApplicationSoftwareRunTimeEnvironment: tag1
GlueHostApplicationSoftwareRunTimeEnvironment: tag2
 
Deleted:
<
<

CREAM

 
Changed:
<
<

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

>
>

Bug #69854 CreamCE should publish non-production state when job submission is disabled - Not Implemented

Disable job submission with glite-ce-disable-submission. Wait 3 minutes and then perform the following ldap query:

# ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=grid" | grep GlueCEStateStatus

For each GlueCE this should return:

GlueCEStateStatus: Draining

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

  STATUS: Implemented
Line: 260 to 330
 
  • 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).
Changed:
<
<
Output should be: "Job submission to this CREAM CE is enabled"
>
>
Output should be: "Job submission to this CREAM CE is disabled"

Bug #77791 CREAM installation does not fail if sudo is not installed - Not Implemented

Try to configure via yaim a CREAM-CE where the sudo executable is not installed,

The configuration should fail saying:

 
Added:
>
>
 ERROR: sudo probably not installed !

Fixes provided with CREAM 1.13.3

 
Changed:
<
<

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment. - Implemented

>
>

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment. - Implemented

  STATUS: Implemented
Line: 286 to 368
 STOP jobAdminPurger
Deleted:
<
<

Bug #81824 yaim-cream-ce should manage the attribute bupdater_loop_interval. - Implemented

 
Deleted:
<
<
STATUS: Implemented
 
Changed:
<
<
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

>
>

Bug #83238 Sometimes CREAM does not update the state of a failed job. - Implemented

  STATUS: Implemented
Line: 305 to 384
  FailureReason = [Job has been terminated (got SIGTERM)]
Changed:
<
<

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Not implemented

>
>

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Not implemented

  STATUS: Not implemented
Line: 316 to 395
 
  • 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
Changed:
<
<

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - Implemented

>
>

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - Implemented

  STATUS: Implemented
Line: 340 to 419
  should appear.
Changed:
<
<

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Implemented

>
>

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Implemented

 

STATUS: Implemented

Line: 353 to 432
  It should not find anything
Changed:
<
<

Bug #87361 The attribute cream_concurrency_level should be configurable via yaim. - Implemented

>
>

Bug #87361 The attribute cream_concurrency_level should be configurable via yaim. - Implemented

  STATUS: Implemented
Line: 363 to 442
  cream_concurrency_level="n"
Changed:
<
<

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Not implemented

>
>

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Not implemented

  STATUS: Not implemented

Revision 172012-01-03 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 467 to 467
 WORKING_AREA_MULTISLOT_TOTAL WORKING_AREA_MULTISLOT_FREE WORKING_AREA_MULTISLOT_LIFETIME
Changed:
<
<
>
>
  and then configure via yaim. Then query the resource bdii of the gLite cluster and verify that the relevant attributes of the glue2 ComputingManager object are set.
Line: 577 to 577
  Check if the returned information is correct.
Added:
>
>

Bug #90113 missing yaim check for batch system - Not implemented

To test the fix, configure a CREAM CE without having also installed LSF.

yaim installation should fail saying that there were problems with LSF installation.

  -- MassimoSgaravatto - 2011-11-07 \ No newline at end of file

Revision 162012-01-02 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 438 to 438
 
Added:
>
>

Bug #87691 Not possible to map different queues of the same CE to different clusters - Not implemented

To test this fix, configure a gLite-CLUSTER with at least two different queues mapped to different clusters (use the yaim variables QUEUE__CLUSTER_UniqueID), e.g."

QUEUE_CREAMTEST1_CLUSTER_UniqueID=cl1id
QUEUE_CREAMTEST2_CLUSTER_UniqueID=cl2id

Then query the resource bdii of the gLite-CLUSTER and verify that:

  • for the GlueCluster objectclass with GlueClusterUniqueID equal to cl1id, the attributes GlueClusterService and GlueForeignKey refers to CEIds with creamtest1 as queue
  • for the GlueCluster objectclass with GlueClusterUniqueID equal to cl2id, the attributes GlueClusterService and GlueForeignKey refers to CEIds with creamtest2 as queue

Bug #87799 Add yaim variables to configure the GLUE 2 WorkingArea attributes - Not implemented

Set all (or some) of the following yaim variables:

WORKING_AREA_SHARED
WORKING_AREA_GUARANTEED
WORKING_AREA_TOTAL
WORKING_AREA_FREE
WORKING_AREA_LIFETIME
WORKING_AREA_MULTISLOT_TOTAL
WORKING_AREA_MULTISLOT_FREE
WORKING_AREA_MULTISLOT_LIFETIME
<verbatim>

and then configure via yaim. Then query the resource bdii of the gLite cluster and verify that the relevant attributes of the glue2 ComputingManager object are set.

</verbatim>
<nop>
 

CREAM Torque module

Revision 152011-12-31 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 386 to 386
 

gLite-CLUSTER

Added:
>
>

Bug #69318 The cluster publisher needs to publish in GLUE 2 too Not implemented

ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingService

ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Manager

  • Check if the resource BDII publishes glue 2 GLUE2Share objectclasses. There should be one GLUE2Share objectclass per each VOview.

ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Share

ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment

ldapsearch -h  <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"

Bug #86512 YAIM CLuster Publisher incorrectly configures GlueClusterService and GlueForeignKey for CreamCEs- Not implemented

To test the fix issue a ldapsearch such as:

ldapsearch -h <gLite-CLUSTER> -x -p 2170 -b "o=grid" | grep GlueClusterService

Then issue a ldapsearch such as:

ldapsearch -h  <gLite-CLUSTER> -x -p 2170 -b "o=grid" | grep GlueForeignKey | grep -v Site

Verify that for each returned line, the format is:

<hostname>:8443/cream-<lrms>-<queue>

 

CREAM Torque module

Added:
>
>

Bug #17325 Default time limits not taken into account - Not implemented

To test the fix for this bug, consider a PBS installation where for a certain queue both default and max values are specified, e.g.:

resources_max.cput = A
resources_max.walltime = B
resources_default.cput = C
resources_default.walltime = D

Verify that the published value for GlueCEPolicyMaxCPUTime is C and that the published value for GlueCEPolicyMaxWallClockTime is D

Bug #49653 lcg-info-dynamic-pbs should check pcput in addition to cput - Not implemented

To test the fix for this bug, consider a PBS installation where for a certain queue both cput and pcput max values are specified, e.g.:

resources_max.cput = A
resources_max.pcput = B

Verify that the published value for GlueCEPolicyMaxCPUTime is the minimum between A an B.

Then consider a PBS installation where for a certain queue both cput and pcput max and default values are specified, e.g.:

resources_max.cput = C
resources_default.cput = D
resources_max.pcput = E
resources_default.pcput = F

Verify that the published value for GlueCEPolicyMaxCPUTime is the minimum between D and F.

Bug #76162 YAIM for APEL parsers to use the BATCH_LOG_DIR for the batch system log location - Not implemented

To test the fix for this bug, set the yaim variable BATCH_ACCT_DIR and configure via yaim.

Check the file /etc/glite-apel-pbs/parser-config-yaim.xml and verify the section:

<Logs searchSubDirs="yes" reprocess="no">
            <Dir>X</Dir>

X should be the value specified for BATCH_ACCT_DIR.

Then reconfigure without setting BATCH_ACCT_DIR.

Check the file /etc/glite-apel-pbs/parser-config-yaim.xml and verify that the directory name is ${TORQUE_VAR_DIR}/server_priv/accounting

Bug #77106 PBS info provider doesn't allow - in a queue name - Not implemented

To test the fix, configure a CREAM CE in a PBS installation where at least a queue has a - in its name.

Then log as root on the CREAM CE and run:

/sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-ce"

Check if the returned information is correct.

 

CREAM LSF module

Bug #88720 Too many '9' in GlueCEPolicyMaxCPUTime for LSF - Not implemented

Line: 421 to 541
 /sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-ce"
Changed:
<
<
Check if in the DNs of the glue1 GlueCE objectclasses and of the glue2 Glue2Share objectclasses the name of the queue is correct.
>
>
Check if the returned information is correct.
 

-- MassimoSgaravatto - 2011-11-07

Revision 142011-12-30 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 383 to 383
  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.
Added:
>
>

gLite-CLUSTER

CREAM Torque module

CREAM LSF module

Bug #88720 Too many '9' in GlueCEPolicyMaxCPUTime for LSF - Not implemented

To test the fix, query the CREAM CE resource bdii in the following way:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=grid" | grep GlueCEPolicyMaxCPUTime | grep 9999999999

This shouldn't return anything.

Bug #89767 The LSF dynamic infoprovider shouldn't publish GlueCEStateFreeCPUs and GlueCEStateFreeJobSlots - Not implemented

To test the fix, log as root on the CREAM CE and run:

/sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-ce"

Among the returned information, there shouldn't be GlueCEStateFreeCPUs and GlueCEStateFreeJobSlots.

Bug #89794 LSF info provider doesn't allow - in a queue name - Not implemented

To test the fix, configure a CREAM CE in a LSF installation where at least a queue has a - in its name.

Then log as root on the CREAM CE and run:

/sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-ce"

Check if in the DNs of the glue1 GlueCE objectclasses and of the glue2 Glue2Share objectclasses the name of the queue is correct.

 -- MassimoSgaravatto - 2011-11-07

Revision 132011-12-22 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 28 to 28
 Add:
lsf_batch_caching_enabled=yes
Changed:
<
<
batch_command_caching_filter=/usr/bin/runcmd.p
>
>
batch_command_caching_filter=/usr/bin/runcmd.pl
  in /etc/blah.config.
Line: 43 to 43
 $numArgs = $#ARGV + 1; open (MYFILE, '>>/tmp/xyz'); foreach $argnum (0 .. $#ARGV) {
Changed:
<
<
print MYFILE "$ARGV[$argnum]\n";
>
>
print MYFILE "$ARGV[$argnum] ";
 }
Added:
>
>
print MYFILE "\n";
 close (MYFILE);
Line: 68 to 69
  Check permissions and ownership under /var/blah. They should be:
Added:
>
>
 /var/blah: total 12 -rw-r--r-- 1 tomcat tomcat 5 Oct 18 07:32 blah_bnotifier.pid
Line: 88 to 90
  /var/blah/user_blah_job_registry.bjr/registry.proxydir: total 0
Changed:
<
<
>
>
 

Bug #81354 (Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute causes thread to loop) Not implemented

Log on a cream ce as user tomcat.

Line: 133 to 135
 Submit a job directly to CREAM using CREAM-CLI. Then submit a job to CREAM through the WMS.
Changed:
<
<
In the accounting log file (/var/log/cream/accounting/blahp.log-) in both cases the clientID field should end with the numeric part of the CREAM jobid, e.g.:
>
>
In the accounting log file (/var/log/cream/accounting/blahp.log-<date>) in both cases the clientID field should end with the numeric part of the CREAM jobid, e.g.:
 
"timestamp=2011-10-10 14:37:38" "userDN=/C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto" "userFQAN=/dteam/Role=NULL/Capability=NULL" "userFQAN=/dteam/NGI_IT/Role=NULL/Capability=NULL" "ceID=cream-38.pd.infn.it:8443/cream-pbs-creamtest2" "jobID=CREAM956286045" "lrmsID=300.cream-38.pd.infn.it" "localUser=18757" "clientID=cre38_956286045"
Line: 160 to 162
 

Bug #83275 (Problem in updater with very short jobs that can cause no notification to cream) Not implemented

Changed:
<
<
Configure a CREAM CE using the old blparser.
>
>
Configure a CREAM CE using the new blparser.
 Submit a job using the following JDL:
Line: 170 to 172
 ]
Changed:
<
<
Check in the bnotifier log file (=/var/log/cream/glite-ce-bnotifier.log=_ that a lest a notification is sent for this job, e.g.:
>
>
Check in the bnotifier log file (/var/log/cream/glite-ce-bnotifier.log that at least a notification is sent for this job, e.g.:
 
2011-11-04 14:11:11 Sent for Cream:[BatchJobId="927.cream-38.pd.infn.it"; JobStatus=4; ChangeTime="2011-11-04 14:08:55"; JwExitCode=0; Reason="reason=0"; ClientJobId="622028514"; BlahJobName="cre38_622028514";]

Revision 122011-12-20 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 202 to 202
 root 26485 0.0 0.2 155564 5868 ? Sl 07:36 0:00 /usr/bin/BLParserPBS -d 1 -l /var/log/cream/glite-pbsparser.log -s /var/torque -p 33333 -m 56565
Added:
>
>

Bug #88974 BUpdaterSGE and BNotifier don't start if sge_helperpath var is not fixed Not implemented

Install and configure (via yaim) a CREAM-CE using GE as batch system.

Make sure that in /etc/blah.config the variable sge_helperpath is commented/is not there.

Try to restart the blparser: /etc/init.d/glite-ce-blahparser restart

It should work without problems. In particular it should not report the following error:

Starting BNotifier: /usr/bin/BNotifier: sge_helperpath not defined. Exiting
[FAILED]
Starting BUpdaterSGE: /usr/bin/BUpdaterSGE: sge_helperpath not defined. Exiting
[FAILED] 

Bug 89859 There is a memory leak in the updater for LSF, PBS and Condor Not implemented

Configure a CREAM CE using the new blparser.

Submit 1000 jobs using e.g. this JDL:

[
executable="/bin/sleep";
arguments="100";
]

Keep monitoring the memory used by the bupdaterxxx process. It should basically not increase.

The test should be done for both LSF and Torque/PBS.

 

CREAM

Revision 112011-12-19 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 63 to 63
 ...
Added:
>
>

Bug #80805 (BLAH job registry permissions should be improved) Not implemented

Check permissions and ownership under /var/blah. They should be:

/var/blah: total 12 -rw-r--r-- 1 tomcat tomcat 5 Oct 18 07:32 blah_bnotifier.pid -rw-r--r-- 1 tomcat tomcat 5 Oct 18 07:32 blah_bupdater.pid drwxrwx--t 4 tomcat tomcat 4096 Oct 18 07:38 user_blah_job_registry.bjr

/var/blah/user_blah_job_registry.bjr: total 16 -rw-rw-r-- 1 tomcat tomcat 1712 Oct 18 07:38 registry -rw-r--r-- 1 tomcat tomcat 260 Oct 18 07:38 registry.by_blah_index -rw-rw-rw- 1 tomcat tomcat 0 Oct 18 07:38 registry.locktest drwxrwx-wt 2 tomcat tomcat 4096 Oct 18 07:38 registry.npudir drwxrwx-wt 2 tomcat tomcat 4096 Oct 18 07:38 registry.proxydir -rw-rw-r-- 1 tomcat tomcat 0 Oct 18 07:32 registry.subjectlist

/var/blah/user_blah_job_registry.bjr/registry.npudir: total 0

/var/blah/user_blah_job_registry.bjr/registry.proxydir: total 0

Bug #81354 (Missing 'Iwd' Attribute when trasferring files with the 'TransferInput' attribute causes thread to loop) Not implemented

Log on a cream ce as user tomcat. Create a proxy of yours and copy it as /tmp/proxy (change the ownership to tomcat.tomcat).

Create the file /home/dteam001/dir1/fstab (you can copy /etc/fstab).

Submit a job directly via blah (in the following change pbs and creamtest2 with the relevant batch system and queue names):

$ /usr/bin/blahpd
$GahpVersion: 1.16.2 Mar 31 2008 INFN\ blahpd\ (poly,new_esc_format) $
BLAH_SET_SUDO_ID dteam001
S Sudo\ mode\ on
blah_job_submit 1 [cmd="/bin/cp";Args="fstab\ fstab.out";TransferInput="/home/dteam001/dir1/fstab";TransferOutput="fstab.out";TransferOutputRemaps="fstab.out=/home/dteam001/dir1/fstab.out";gridtype="pbs";queue="creamtest2";x509userproxy="/tmp/proxy"]
S
results
S 1
1 0 No\ error pbs/20111010/304.cream-38.pd.infn.it

Eventually check the content of /home/dteam001/dir1/ where you see both fstab and fstab.out:

$ ls /home/dteam001/dir1/
fstab  fstab.out

Bug #81824 (yaim-cream-ce should manage the attribute bupdater_loop_interval) Not implemented

Set BUPDATER_LOOP_INTERVAL to 30 in siteinfo.def and reconfigure via yaim. Then verify that in blah.config there is:

bupdater_loop_interval=30

Bug #82281 (blahp.log records should always contain CREAM job ID) Not implement

Submit a job directly to CREAM using CREAM-CLI. Then submit a job to CREAM through the WMS.

In the accounting log file (/var/log/cream/accounting/blahp.log-) in both cases the clientID field should end with the numeric part of the CREAM jobid, e.g.:

"timestamp=2011-10-10 14:37:38" "userDN=/C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto" "userFQAN=/dteam/Role=NULL/Capability=NULL" "userFQAN=/dteam/NGI_IT/Role=NULL/Capability=NULL" "ceID=cream-38.pd.infn.it:8443/cream-pbs-creamtest2" "jobID=CREAM956286045" "lrmsID=300.cream-38.pd.infn.it" "localUser=18757" "clientID=cre38_956286045"

"timestamp=2011-10-10 14:39:57" "userDN=/C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto" "userFQAN=/dteam/Role=NULL/Capability=NULL" "userFQAN=/dteam/NGI_IT/Role=NULL/Capability=NULL" "ceID=cream-38.pd.infn.it:8443/cream-pbs-creamtest2" "jobID=https://devel19.cnaf.infn.it:9000/dLvm84LvD7w7QXtLZK4L0A" "lrmsID=302.cream-38.pd.infn.it" "localUser=18757" "clientID=cre38_315532638"

Bug #82297 (blahp.log rotation period is too short) Not implemented

Check that in /etc/logrotate.d/blahp-logrotate rotate is equal to 365:

# cat /etc/logrotate.d/blahp-logrotate
/var/log/cream/accounting/blahp.log {
        copytruncate
        rotate 365
        size = 10M
        missingok
        nomail
}

Bug #83275 (Problem in updater with very short jobs that can cause no notification to cream) Not implemented

Configure a CREAM CE using the old blparser. Submit a job using the following JDL:

[
executable="/bin/echo";
arguments="ciao";
]

Check in the bnotifier log file (=/var/log/cream/glite-ce-bnotifier.log=_ that a lest a notification is sent for this job, e.g.:

2011-11-04 14:11:11 Sent for Cream:[BatchJobId="927.cream-38.pd.infn.it"; JobStatus=4; ChangeTime="2011-11-04 14:08:55"; JwExitCode=0; Reason="reason=0"; ClientJobId="622028514"; BlahJobName="cre38_622028514";]

Bug #83347 (Incorrect special character handling for BLAH Arguments and Environment attributes) Not implemented

Log on a cream ce as user tomcat. Create a proxy of yours and copy it as /tmp/proxy (change the ownership to tomcat.tomcat).

Create the file /home/dteam001/dir1/fstab (you can copy /etc/fstab).

Submit a job directly via blah (in the following change pbs and creamtest1 with the relevant batch system and queue names):

BLAH_JOB_SUBMIT 1 [Cmd="/bin/echo";Args="$HOSTNAME";Out="/tmp/stdout_l15367";In="/dev/null";GridType="pbs";Queue="creamtest1";x509userproxy="/tmp/proxy";Iwd="/tmp";TransferOutput="output_file";TransferOutputRemaps="output_file=/tmp/stdout_l15367";GridResource="blah"]

Verify that in the output file there is the hostname of the WN.

Bug #87419 (blparser_master add some spurious character in the BLParser command line) Not implemented

Configure a CREAM CE using the old blparser. Check the blparser process using ps. It shouldn't show urious characters:

root     26485  0.0  0.2 155564  5868 ?        Sl   07:36   0:00 /usr/bin/BLParserPBS -d 1 -l /var/log/cream/glite-pbsparser.log -s /var/torque -p 33333 -m 56565


 

CREAM

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

Revision 102011-12-19 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Added:
>
>

BLAH

Bug #75854 Problems related to the growth of the blah registry) Not implemented

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:

[
executable="/bin/sleep";
arguments="100";
]

Monitor the BLAH processed. Verify that each of them doesn't use more than 50 MB.

Bug #77776 (BUpdater should have an option to use cached batch system commands) Not implemented

Add:

lsf_batch_caching_enabled=yes
batch_command_caching_filter=/usr/bin/runcmd.p
in /etc/blah.config.

Create and fill /usr/bin/runcmd.pl with the following content:

#!/usr/bin/perl
#---------------------#
#  PROGRAM:  argv.pl  #
#---------------------#

$numArgs = $#ARGV + 1;
open (MYFILE, '>>/tmp/xyz');
foreach $argnum (0 .. $#ARGV) {
    print MYFILE "$ARGV[$argnum]\n";
}
close (MYFILE); 

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:

/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
...

CREAM

 

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

STATUS: Implemented

Revision 92011-12-06 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 98 to 98
  should appear.
Changed:
<
<

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Not implemented

>
>

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Implemented

 
Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix, issue the following ldapsearch query towards the resource bdii of the CREAM-CE:

Revision 82011-12-05 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 74 to 74
 
  • 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
Changed:
<
<

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - Not implemented

>
>

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - Implemented

 
Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix, query the resource bdii of the CREAM-CE:

Revision 72011-12-01 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Changed:
<
<

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled

>
>

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled - Implemented

  STATUS: Implemented
Line: 21 to 21
 Output should be: "Job submission to this CREAM CE is enabled"
Changed:
<
<

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment.

>
>

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment. - Implemented

  STATUS: Implemented
Line: 44 to 44
 STOP jobAdminPurger
Changed:
<
<

Bug #81824 yaim-cream-ce should manage the attribute bupdater_loop_interval

>
>

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.

Changed:
<
<

Bug #83238 Sometimes CREAM does not update the state of a failed job

>
>

Bug #83238 Sometimes CREAM does not update the state of a failed job. - Implemented

 
Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix, try to kill by hand a job.
Line: 63 to 63
  FailureReason = [Job has been terminated (got SIGTERM)]
Changed:
<
<

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed

>
>

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed. - Not implemented

  STATUS: Not implemented
Line: 74 to 74
 
  • 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
Changed:
<
<

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=

>
>

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=. - Not implemented

  STATUS: Not implemented
Line: 98 to 98
  should appear.
Changed:
<
<

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView

>
>

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView - Not implemented

  STATUS: Not implemented
Line: 110 to 111
  It should not find anything
Changed:
<
<

Bug #87361 The attribute cream_concurrency_level should be configurable via yaim

>
>

Bug #87361 The attribute cream_concurrency_level should be configurable via yaim. - Implemented

  STATUS: Implemented
Line: 120 to 121
  cream_concurrency_level="n"
Changed:
<
<

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment".

>
>

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment". - Not implemented

  STATUS: Not implemented

Revision 62011-11-16 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix:
  • disable the submission on the CE
Line: 23 to 23
 

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment.

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Implemented
  To test the fix, simply run on the CREAM CE as root the JobDBAdminPurger.sh. E.g.:
Line: 46 to 46
 

Bug #81824 yaim-cream-ce should manage the attribute bupdater_loop_interval

Changed:
<
<
STATUS: Not 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

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Not implemented
  To test the fix, try to kill by hand a job.
Line: 65 to 65
 

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed

Changed:
<
<
STATUS: 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.
Line: 76 to 76
 

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Not implemented
  To test the fix, query the resource bdii of the CREAM-CE:
Line: 100 to 100
 

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Not implemented
  To test the fix, issue the following ldapsearch query towards the resource bdii of the CREAM-CE:
Line: 112 to 112
 

Bug #87361 The attribute cream_concurrency_level should be configurable via yaim

Changed:
<
<
STATUS: Not 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:
Line: 122 to 122
 

Bug #87492 CREAM doesn't handle correctly the jdl attribute "environment".

Changed:
<
<
STATUS: Not implemented
>
>
STATUS: Not implemented
  To test the fix, submit the following JDL using glite-ce-job-submit:

Revision 52011-11-11 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 20 to 20
  Output should be: "Job submission to this CREAM CE is enabled"
Deleted:
<
<

Bug #79026 config_cream_sudoers creates wrong sudoers file when the same gid is shared

TBD

 

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment.

Revision 42011-11-08 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 19 to 19
 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"

Changed:
<
<
>
>
 

Bug #79026 config_cream_sudoers creates wrong sudoers file when the same gid is shared

TBD

Line: 48 to 47
 STOP jobAdminPurger
Added:
>
>

Bug #81824 yaim-cream-ce should manage the attribute bupdater_loop_interval

STATUS: Not 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

STATUS: Not implemented

Revision 32011-11-08 - SaraBertocco

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Added:
>
>

Bug #69857 Job submission to CreamCE is enabled by restart of service even if it was previously disabled

 
Added:
>
>
STATUS: Not 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 #79026 config_cream_sudoers creates wrong sudoers file when the same gid is shared

TBD

Line: 50 to 66
  STATUS: Not implemented
Changed:
<
<
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.
>
>
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:
Line: 99 to 113
  STATUS: Not implemented
Changed:
<
<
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:
>
>
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"

Revision 22011-11-07 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Added:
>
>

Bug #79026 config_cream_sudoers creates wrong sudoers file when the same gid is shared

TBD

 

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment.

STATUS: Not implemented

Line: 29 to 33
 

Bug #83238 Sometimes CREAM does not update the state of a failed job

Added:
>
>
STATUS: Not implemented
 To test the fix, try to kill by hand a job.

The status of the job should eventually be:

Line: 40 to 46
 
Added:
>
>

Bug #83749 JobDBAdminPurger cannot purge jobs if configured sandbox dir has changed

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:

 
Added:
>
>
  • 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
 

Bug #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=

Line: 67 to 83
  should appear.
Added:
>
>

Bug #86191 No info published by the lcg-info-dynamic-scheduler for one VOView

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

STATUS: Not 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".

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

Revision 12011-11-07 - MassimoSgaravatto

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Bug #81561 Make JobDBAdminPurger script compliant with CREAM EMI environment.

STATUS: Not 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 #83238 Sometimes CREAM does not update the state of a failed job

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 #84374 yaim-cream-ce: GlueForeignKey: GlueCEUniqueID: published using : instead of=

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.

-- MassimoSgaravatto - 2011-11-07

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback