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

 

 

gLite 3.1

glite-WN - Update to version 3.1.15-0


Date 29.04.1009
Priority Normal

Description


Refer to the main release note for all informations For the release Note :
../../../../../../../../glite-web/egee/packages/R3.1/x86_64/updates.asp
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
 #37009 Resolving a WN to GlueSubCluster attributes must be possible from a running job.
 #42943 [ yaim-clients ] config_vomsdir has to be included in the TAR UI and TAR WN
 #45442 [ yaim-clients ] Add config_wn_info in WN and TAR WN
 #45446 [ yaim-core ] WN_LIST example file should be updated
 #45649 [ yaim-core ] PYTHON_PATH should be set to Python version specific directories as well
 #45852 [ yaim-core ] PYTHONPATH entries are wrongly ordered
 #46299 [ yaim-core ] incorrect here-doc syntax in config_mkgridmap
 #46633 [ yaim-core ] Add new variables in site-info.def
 #46848 [ yaim-clients ] Duplicated definition of PYTHONPATH and PERL5LIB
 #46965 [ yaim-core ] users.conf and groups.conf for PILOT jobs
 #46975 [ yaim-core ] VO_voname_DEFAULT_SE is not populated with value from SE_LIST

Updated rpms

Name Version Full RPM name Description
glite-WN-version 3.1.15-0 glite-WN-version-3.1.15-0.x86_64.rpm Version tag/marker for glite-WN
glite-wn-info 1.0.2-2 glite-wn-info-1.0.2-2.noarch.rpm glite-wn-info supplies information on the WN.
glite-yaim-clients 4.0.7-3 glite-yaim-clients-4.0.7-3.noarch.rpm UI, WN and VOBOX configuration
glite-yaim-core 4.0.7-9 glite-yaim-core-4.0.7-9.noarch.rpm YAIM core package
GFAL-client 1.11.4-1.slc4 GFAL-client-1.11.4-1.slc4.x86_64.rpm org.glite.data.gfal v1.11.4-1
GFAL-client 1.11.4-1.slc4 GFAL-client-1.11.4-1.slc4.i386.rpm org.glite.data.gfal v1.11.4-1
lcg_util 1.7.2-1.slc4 lcg_util-1.7.2-1.slc4.x86_64.rpm org.glite.data.dm-util v1.7.2-1
lcg_util 1.7.2-1.slc4 lcg_util-1.7.2-1.slc4.i386.rpm org.glite.data.dm-util v1.7.2-1

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)