gLite > gLite 3.1 > glite-WN > Update to glite-WN 3.1.17-0  
 
 

 

 

gLite 3.1

glite-WN - Update to version 3.1.17-0


Date 16.06.2009
Priority Normal

Description

glite-WN
  • The WN includes the myproxy client that was missing in its dependencies
  • Minor release of GFAL 1.11.6-1: Fix of error handling regression bug
  • Minor release of lcg_util 1.7.4-1:
    • warning in case of mismatch between command line VO and proxy VO
    • asynchronous srmLs support (dCache)
    • new synchronous function gfal_bringonline() with retrying/polling mechanism
    • new lcg-get-checksum command (and corresponding API function)
    • SRMv2 is now used by default if available
    • support of checksum verification during file transfers

Known Issues in lcg_utils
  • When copying a local file to an SE, checksum checking does not work. (SE -> local and SE -> SE works OK). Will be fixed for the next release.
  • The lcg-rf commmand no longer prints the guid on success. The "--verbose" option has to be used in order to obtain the value. See bug #50548


Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #38801 WN needs MyProxy client

Updated rpms

Name Version Full RPM name Description
GFAL-client 1.11.6-2.slc4 GFAL-client-1.11.6-2.slc4.i386.rpm org.glite.data.gfal v1.11.6-2
GFAL-client 1.11.6-2.slc4 GFAL-client-1.11.6-2.slc4.x86_64.rpm org.glite.data.gfal v1.11.6-2
glite-WN-version 3.1.17-0 glite-WN-version-3.1.17-0.x86_64.rpm Version tag/marker for glite-WN
lcg_util 1.7.4-1.slc4 lcg_util-1.7.4-1.slc4.i386.rpm org.glite.data.dm-util v1.7.4-1
lcg_util 1.7.4-1.slc4 lcg_util-1.7.4-1.slc4.x86_64.rpm org.glite.data.dm-util v1.7.4-1
myproxy VDT1.6.1x86_64_rhas_4-7 myproxy-VDT1.6.1x86_64_rhas_4-7.x86_64.rpm Virtual Data Toolkit

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)