Difference: CreamTestsRdot1dot9 (1 vs. 6)

• BUG #36206: HOPEFULLY FIXED
  • Cannot reproduce

• BUG #38029: HOPEFULLY FIXED
  • Cannot reproduce

• BUG #38629: FIXED
  • submit a job using a proxy expirying in a 10 minutes
  • verify with the command glite-ce-job-status that the status of the job is DONE-FAILED

• BUG #38631: HOPEFULLY FIXED
  • cannot reproduce

• BUG #39131: HOPEFULLYFIXED

• BUG #39132: HOPEFULLY FIXED

• BUG #39656: HOPEFULLY FIXED
  • cannot reproduce

• BUG #41036: HOPEFULLY FIXED
  • cannot reproduce

• BUG #38420: NOT FIXED

• BUG #37851: FIXED
  • change the permission mask of the the file /opt/glite/sbin/glexec from 4750 to 750
  • submit a job, specifying the inputsandbox, and verify that the fault reason contains: "The problem seems to be related to glexec"

• BUG #38420: CANNOT TEST
  • set the following parameters:

    <parameter name="JOB_PURGE_RATE" value="5" /> <!-- minutes -->
        <parameter name="JOB_PURGE_POLICY" value="ABORTED 5 minutes ; CANCELLED 5 minutes ; 
                           DONE-OK 5 minutes ; DONE-FAILED 5 minutes ; REGISTERED 5 minutes ;" />

    in the commandexecutor section of the cream configuration
  • submit a short-lived job (10 minutes) and verify the "really-running" status
  • wait 20 minutes and verify that the job has been purged

• BUG #39131: PROBABLY FIXED
  • to be verified with a profiler

• BUG #39132: PROBABLY FIXED
  • to be verified with a profiler

• BUG #40920: FIXED
  • trivial to test

• BUG #41036: PROBABLY FIXED

• BUG #37683: FIXED
  • shut down the BLParser daemon (/opt/glite/etc/init.d/glite-ce-blparser stop)
  • submit a job to the related CE and verify that the fault reason is "The job cannot be submitted because the blparser service is not alive"
  • restart the BLParser daemon and wait 5 minutes
  • submit a job a new job and verify the correct execution

• BUG #40331: FIXED
  • insert the following tag:

        <plugin name="ban-plugin"
                classname="org.glite.security.authz.pdp.BlackListServicePDP">
          <parameter name="blackListFile"
                     value="/opt/glite/etc/glite-ce-cream/banned.lst" />
        </plugin>
    

    in the authzchain section of the cream configuration
  • insert the user DN into the file /opt/glite/etc/glite-ce-cream/banned.lst
  • restart the service
  • execute a glite-ce-job-list and verify that the fault contains "policyDecision"

Check bugs:

• BUG #36413: FIXED
  • Shut down the service
  • Insert the following tag into the file: /opt/glite/etc/glite-ce-monitor/cemonitor-config.xml

      <subscription id="subscription-1"
            monitorConsumerURL="address_of_the_consumer"
            subscriberId="DN_of_the_consumer"
            sslprotocol="SSLv3"
            retryCount="-1">
        <topic name="CREAM_JOBS">
          <dialect name="CLASSAD" />
        </topic>
        <policy rate="30">
          <query queryLanguage="ClassAd">true</query>
          <action name="SendNotification" doActionWhenQueryIs="true" />
          <action name="SendExpiredNotification" doActionWhenQueryIs="false" />
        </policy>
      </subscription>
    

    specifying the correct address_of_the_consumer and DN_of_the_consumer values
  • start the CEMonitor consumer with SSL support
  • start the service
  • more than one notification must appear on the output of the CEMonitor consumer

• BUG #36469: FIXED
  • same recipe as for bug #36413 but specify two different subscriptions, the first one refers to a not existing consumer
  • start both consumer and service
  • notifications must appear on the output of the CEMonitor consumer and and error must be logged on the CEMonitor log

-- PaoloAndreetto - 09 Sep 2008