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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TODO Bug #98440 Missing revision number in EndpointImplementationVersion Not Implemented

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

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

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

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

TODOBug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

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

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

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

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

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

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

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

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

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

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

TODOBug #95184 Missing real value for GlueCEPolicyMaxSlotsPerJob Not Implemented

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

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

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

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

Fixes provided with CREAM 1.14.6

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

#CREAM-127

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

#CREAM-113

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

#CREAM-124

Fixes provided with CREAM TORQUE module 2.1.2

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

CREAM #119

CREAM SLURM module

Fixes provided with CREAM SLURM module 1.0.1

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

CREAM #116

Fixes provided with BLAH 1.20.3

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

#CREAM-112

Fixes provided with CREAM 1.16.2

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

#CREAM-113

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

#CREAM-124

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

#CREAM-125

Fixes provided with CREAM TORQUE module 2.1.1

CREAM #101 - Wrong time format for MaxWallClockTime Not Implemented

CREAM #101

CREAM #107 - Bad timezone format Not Implemented

CREAM #107

Fixes provided with CREAM LSF module 2.0.3

CREAM #114 - Execution error: Uncaught exception Not Implemented

CREAM #114

Fixes provided with BLAH 1.18.4

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

#CREAM-94

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

#CREAM-105

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

#CREAM-112

Fixes provided with CREAM 1.16.1

Fixes provided with CREAM 1.14.5

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

#CREAM-111

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

#CREAM-101

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

#CREAM-99

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

#CREAM-84

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

#CREAM-83

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

#CREAM-82

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

#CREAM-78

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

#CREAM-77

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

Fixes provided with BLAH 1.20.2

Bug #CREAM-88 Memory leak in BNotifier Not Implemented

#CREAM-88

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

#CREAM-94

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

#CREAM-105

Bug #CREAM-107 Bad timezone format Not Implemented

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

Bug #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

Bug #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

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

Bug #CREAM-74 Remove trustmanager from the provides list of cream-common 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

Bug #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 Not Implemented

Bug #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 Not Implemented

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

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

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

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

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

Bug #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 Not Implemented

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

#CREAM-75

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

#CREAM-83

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

#CREAM-84

Bug #CREAM-88 Memory leak in BNotifier

#CREAM-88

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

#CREAM-89

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

#CREAM-90

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

#CREAM-91

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

#CREAM-94

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

#CREAM-102

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

#CREAM-105

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

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

CREAM

• #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 #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

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.

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

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

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

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

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

• run the command

  /sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-cream-glue2" |grep ServingState

• insert several spurious lines within the block of job data, it's better to insert also some empty lines.

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

• 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.

• 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                
  [...]

• 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...
  

• 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 #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

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

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

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

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

Fixes provided with CREAM 1.14.3

• 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

• 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:

• On the UI prepare a jdl for executing the above script: example

• 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 #96306 Wrong lowercase conversion for VO Tags Implemented

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

• 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.

• 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 #95328 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

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 "

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

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

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

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

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 #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

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 #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.

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)

• submit a job

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

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

• 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 #95382 In cluster mode, YAIM does not set GlueCEInfoHostName for CREAMs Not Implemented

Bug #95973 Missing Glue capability in GLUE2EntityOtherInfo Not Implemented

Bug #96306 Wrong lowercase conversion for VO Tags Not 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

• 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

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

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.2

• [EMI1]

• [EMI2]

            commandworkerpoolsize="n"
  

Bug #59871 lcg-info-dynamic-software must split tag lines on white space - 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)

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

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

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

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

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

• reconfigure the CE with YAIM (USE_ARGUS=no)

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

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=...)

• 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)

• 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)

• 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 ..."

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

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

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

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

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

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

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

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

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

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

Fixes provided with BLAH 1.16.6

See Fixes provided with BLAH 1.18.1

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

TBD

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

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

/usr/libexec/glite-ce-glue2-endpoint-static /etc/glite-ce-glue2/glite-ce-glue2.conf | grep GLUE2EndpointURL

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 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)

Bug #90331 Not implemented

here

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