Difference: CreamTestsP3179 (28 vs. 29)

Revision 292010-03-01 - PaoloAndreetto

Line: 1 to 1
 

PATCH 3179

Line: 220 to 220
 
    • Not possible to test the fix since we don't have CREAM based CEs with Condor as batch system
Changed:
<
<
  • Bug #57820: [yaim-cream-ce] CREAM-CE publishes GlueServiceDataValue incomplete NOT TESTED
>
>
  • Bug #57820: [yaim-cream-ce] CREAM-CE publishes GlueServiceDataValue incomplete FIXED
    • run the infoprovider: /opt/glite/etc/gip/provider/glite-info-provider-service-cream-wrapper | grep GlueServiceDataValue
    • verify that 3 different values are returned for the GlueServiceDataValue: the version, the DN and the host name of the CE
 
  • Bug #58103: Cream database Query performance FIXED
    • Internal improvement
Line: 229 to 231
 
  • Bug #58109: Wrong value for the "service version" property FIXED
    • verify the property using the command glite-ce-service-info
Changed:
<
<
  • Bug #58119: CREAM CE: publish Production instead of Special as default value for GlueCEStateStatus NOT TESTED
>
>
  • Bug #58119: CREAM CE: publish Production instead of Special as default value for GlueCEStateStatus FIXED
    • verify with /opt/glite/libexec/glite-info-wrapper | grep -i gluecestatestatus
 
  • Bug #59423: RFE: support for ISB/OSB transfers from/to gridftp servers running using credentials NOT TESTED
Line: 287 to 290
 
  • Bug #62070: Possible problem with notification time in BNotifier HOPEFULLY FIXED
    • Not possible to reproduce it according to the developer (M. Mezzadri)
Changed:
<
<
  • Bug #62207: [ yaim-cream ] Enable Glue 2.0 publishing NOT TESTED
>
>
  • Bug #62207: [ yaim-cream ] Enable Glue 2.0 publishing FIXED
    • send the following query to the CE BDII: ldapsearch -x -h $(hostname) -p 2170 -b o=glue and verify that it returns GLUE2 schema and information
 
  • Bug #62436: Possible problem with updater if job remain queued too long FIXED
    • Fixed as reported here: 3 jobs lasting 2 hours were submitted to a CREAM CE with only 2 job slots. For the third one the BNotifier logged the right events (i.e. it didn't log status=4 with failurereason=999)
Line: 296 to 300
 
  • Bug #62893: Possible proxy renewal problem in the CREAM jw NOT TESTED
Changed:
<
<
  • Bug #63398: CREAM jw: removal of token should be retried in case of failure NOT TESTED
>
>
  • Bug #63398: CREAM jw: removal of token should be retried in case of failure FIXED
    • submit the following jdl:
      [
environment= {"__token_file=gsiftp://host/path"};
executable="/bin/sleep";
arguments="30";
]
      specifying existing host and path first and verify that the job terminate successfully; the owner of the token must be the mapped-user.
    • submit the jdl above but specifying a fake host and/or path and verify that the job status reports 3 different failed attempts for taking the token: 
      "/opt/edg/libexec/edg-gridftp-base-rm: error globus_ftp_client: the server responded with an error 500 500-Command failed : System error in unlink: No such file or directory 500-A system call failed: No such file or directory 500 End"
  -- AlessioGianelle - 2010-02-05
View topic | History: r50 < r49 < r48 < r47 | More topic actions...
 
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