Tags:
, view all tags

PATCH 3179

Automatic tests:

Checked bugs:

  • Bug #37430: BLParser should properly filter it's log output

  • Bug #45364: BLAH_JOB_CANCEL should report failure reason

  • Bug #46419: CREAM sandbox area should be scratched when the CREAM DB is scratched FIXED
    • Submit at least one job to the CE and wait for its termination, so that the sandbox area is not empty
    • Increment the value of the parameters creamdb_database_version and/or delegationdb_database_version in the file /opt/glite/etc/glite-ce-cream/cream-config.xml.template
    • reconfigure the node with yaim and check whether the sandbox area is empty

  • Bug #47070: [ yaim-cream ] yaim cream module should support remote mysql setup

  • Bug #47254: Possible problems if the proxy used to talk with CREAM is shorter than 10 minutes FIXED
    • create a voms-proxy whose lifetime is shorter than 10 minutes
    • submit a simple job whose lifetime is shorter than the voms-proxy one and verify its correct termination

  • Bug #47804: Possible problems configuring blah in CREAM-CE for LSF 

  • Bug #48786: Load should be one of the parameter of DISABLE_SUBMISSION_POLICY in CREAM FIXED
    • specify a low load level in the file /opt/glite/bin/glite_cream_load_monitor
    • try to overload the node with the testsuite: cream-test-monitored-submit -r 30 -n 20000 -m 2000 -C 50 -l log4py.conf -j test.jdl -R --sotimeout 60 --vo dteam --valid 02:00 and verify that with high load the submissions are rejected

  • Bug #49497: user proxies on CREAM do not get cleaned up FIXED
    • delegate a proxy whose lifetime is shorter than the parameter delegation_purge_rate of the CREAM configuration file
    • wait for the new proxy cleanup run (at least twice the delegation_purge_rate) and verify that the proxy file has been removed from the directory

  • Bug #50226: yaim-cream-ce should use config_secure_tomcat  

  • Bug #50723: CREAM: check for the jobtype is not case insensitive FIXED
    • submit a job specifying the parameter "jobtype=Normal" in the JDL and verify the correct execution of the job

  • Bug #50875: CREAM: reason for cancelled jobs should be reported FIXED
    • submit and cancel a job using the CREAM CLI command and verify that the reason reports "Cancelled by user"
    • submit and cancel a job using the LRMS command (e.g. qdel) and verify that the reason reports "Cancelled by CE admin"

  • Bug #50876: CREAM reports that the proxy expired even when the problem is in detecting the lifetime of the proxy 

  • Bug #51046: CREAM: DelegProxyInfo info sometimes is wrong FIXED
    • submit a job, wait for its termination and verify the correct lifetime of the proxy

  • Bug #51118: config_cream_glexec doesn't set glexec permissions right 

  • Bug #51124: catalina.out is clogged with grid-proxy-init warnings FIXED
    • submit a job and check the catalina.out file

  • Bug #51128: lcas-suexec.db on CREAM CE should be named lcas-glexec.db for consistency 

  • Bug #51249: [ yaim-cream-ce ] refactor config_cream_db 

  • Bug #51310: Wrong event timestamp FIXED
    • run the consumer server (glite-ce-monitor-consumer) on the client machine
    • create a subscription for the topic CREAM_JOBS on the CE specifying the URL of the consumer server above
    • submit a job and verify the validity of the field TIMESTAMP of any event

  • Bug #51311: Wrong event timestamp generated by the CREAM Job Sensor FIXED

  • Bug #51313: CEMon must not notify the expired events

  • Bug #51705: glexec-wrapper.sh should be removed from CREAM RPM FIXED
    • check the content of glite-ce-cream rpm

  • Bug #51706: yaim-cream-ce: remove "lcg" prefix from JOB_MANAGER 

  • Bug #51892: Exception when using java.text.DateFormat.parse 

  • Bug #51928: BLAH crashes if the cerequirements classad attribute is malformed 

  • Bug #51978: CREAM can be slow to start 

  • Bug #51993: Proxy renewal not very efficient for multiple jobs having the same delegationid 

  • Bug #52020: [ yaim-cream-ce ] Support use of file (besides syslog) for glexec logging

  • Bug #52050: misleading error message "The problem seems to be related to glexec INVALID
    • The CREAM service does not make use of glexec anymore

  • Bug #52051: CEMon must remove all expired subscriptions on start-up FIXED
    • create a subscription for the topic CREAM_JOBS on the CE with a short lifetime
    • shutdown the service and wait for the expiration of the subscription
    • restart the service and verify that the subscription does not exist anymore in the directory /opt/glite/var/cemonitor/subscription

  • Bug #52052: Sometimes the getInfo() operation does not report the right list of topics FIXED
    • enable or disable the CE sensor removing or adding the corresponding tag in the file /opt/glite/etc/glite-ce-monitor/cemonitor-config.xml
    • wait for cemonitor to reload the configuration (usually 10m)
    • verify the availability of the topic using the command glite-ce-monitor-gettopics

  • Bug #52268: BLAH leaves files in /tmp when CErequirements is set 

  • Bug #52577: [ yaim-cream-ce ] create CREAM_GLEXEC_USER_HOME variable  

  • Bug #52651: CREAM file descriptor overuse FIXED
    • try to overload the node with the testsuite: cream-test-monitored-submit -r 30 -n 20000 -m 2000 -C 50 -l log4py.conf -j test.jdl -R --sotimeout 60 --vo dteam --valid 02:00 and verify that with high load the submissions are rejected
    • seek "too many open files" in the CREAM log

  • Bug #52719: Blah doesn't set the 'executable' flag if a local jobwrapper is found 

  • Bug #52942: Missing description for ISB/OSB error in jobwrapper FIXED
    • submit a job with an unreachable host in the inputsandbox or in the outputsandboxbasedesturi parameter
    • verify that the output of the glite-ce-job-status contains the full description of the failure

  • Bug #53124: blparser_master could crash if some variable in blparser.conf are not set 

  • Bug #53459: [CREAM] Provide method to improve the detection of job status changes by ICE 

  • Bug #53499: CREAM job wrapper template should be put outside the jar FIXED
    • check wheter the file /opt/glite/share/webapps/ce-cream.war contains the file WEB-INF/jobwrapper.tpl

  • Bug #54812: lsf_submit.sh job requirement 

  • Bug #54900: [ glite-yaim-cream-ce ] config_cream_tomcat_user should not add tomcat to VO groups 

  • Bug #54949: Some job can remain in running state when BLParser is restarted for both lsf and pbs 

  • Bug #55078: Possible final state not considered in BLParserPBS and BUpdaterPBS 

  • Bug #55420: Allow admin to purge CREAM jobs in a non terminal status FIXED
    • temporary disconnect any WN from the CE, e.g. shutting down the mom server in a TORQUE installation
    • submit a job
    • on the CE with administrator privileges run the command: /opt/glite/sbin/JobDBAdminPurger.sh -u -p -s 2 as described in the wiki page
    • verify with glite-ce-job-list that the job has been purged from the database
    • verify that the sandbox directory of that job has been removed from /opt/glite/var/cream_sandbox
    • remove manually the job from the batch system and reconnect all the WN

  • Bug #55438: BUpdater problems in updating job state with AssignFinalState for all batch systems 

  • Bug #55531: BUpdaterPBS should consider lines like "unable to run job" 

  • Bug #55565: BLAH configuration attribute blah_disable_wn_proxy_renewal fails to disable proxy renewal. 

  • Bug #56075: Job failure reasons missing in the CREAM log file FIXED
    • submit a job with an unreachable host in the inputsandbox or in the outputsandboxbasedesturi parameter
    • verify that in the log file appears the message: failureReason=Cannot move ISB (): error: globus_xio: Unable to connect to xxxx:2811 globus_xio: globus_libc_getaddrinfo failed.globus_common: Name or service not known

  • Bug #56339: [blah] "service glite-ce-blparser restart" does not always work 

  • Bug #56367: CREAM RPM depends on C libs FIXED
    • check if the package of glite-ce-cream contains any elf executable

  • Bug #56518: BLAH blparser doesn't start after boot of the machine 

  • Bug #56697: CREAM logging must be improved when CREAM register operation fails 

  • Bug #56762: CREAM doesn't accept anymore jobs with NodeNumber and/or CpuNumber ! 

  • Bug #57210: BLAH condor_submit script doesn't recognize certain options. 

  • Bug #57307: condor_submit.sh does not support the handling of "local" attributes 

  • Bug #57820: [yaim-cream-ce] CREAM-CE publishes GlueServiceDataValue incomplete 

  • Bug #58103: Cream database Query performance. 

  • Bug #58109: Wrong value for the "service version" property FIXED
    • verify the property using the command glite-ce-service-info

  • Bug #58119: CREAM CE: publish Production instead of Special as default value for GlueCEStateStatus 

  • Bug #59423: RFE: support for ISB/OSB transfers from/to gridftp servers running using credentials 

  • Bug #58659: NullPointerException from getStatus 

  • Bug #58792: JobRegister fails, because cream_sandbox directory doesn't exist FIXED
    • temporary rename the directory /opt/glite/var/cream_sandbox without turning off the service
    • submit a job and verify that the failure reports "cannot create the job's working directory!"

  • Bug #58941: [yaim-cream-ce] lcmaps confs for glexec and gridftp are not fully synchronized (TM) 

  • Bug #59005: Possible problem with hold/resumed jobs in BUpdaterLSF 

  • Bug #59329: Proxy symlinks left in the registry area until purged 

  • Bug #59686: Possible crash of BUpdarePBS due to wrong malloc 

  • Bug #59962: Sometimes the CREAM initialization fails with "UserId = ADMINISTRATOR is not enable for that operation!" error 

  • Bug #60831: Error log message: "CREAM_JOB_SENSOR_HOST parameter not specified!" 

  • Bug #61322: CREAM jw doesn't set GLITE_WMS_RB_BROKERINFO 

  • Bug #61407: Set CE_ID in the cream jw 

  • Bug #61493: [ yaim-cream-ce ] glexec_get_account policy order is wrong 

-- AlessioGianelle - 2010-02-05

Edit | Attach | PDF | History: r50 | r11 < r10 < r9 < r8 | Backlinks | Raw View | More topic actions...
Topic revision: r9 - 2010-02-11 - PaoloAndreetto
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback