gLite > gLite 3.1 > lcg-CE > Update to lcg-CE 3.1.18-0  
 
 

 

 

gLite 3.1

lcg-CE - Update to version 3.1.18-0


Date 01.09.2008
Priority High

Description



Introduction of the latest VDT packages version 1.6.1-7 for 32Bit platform which solves RPATH security issues and fixes GLOBUS proxy chain length limitations affecting LHCb and ALICE.

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
 #37563 Globus proxy chain length limit too low

Updated rpms

Name Version Full RPM name Description
lcg-CE 3.1.18-0 lcg-CE-3.1.18-0.i386.rpm gLite metapackage (lcg-CE)
vdt_globus_essentials VDT1.6.1x86_rhas_4-7 vdt_globus_essentials-VDT1.6.1x86_rhas_4-7.i386.rpm Virtual Data Toolkit
vdt_globus_jobmanager_common VDT1.6.1x86_rhas_4_LCG-3 vdt_globus_jobmanager_common-VDT1.6.1x86_rhas_4_LCG-3.i386.rpm vdt_globus_jobmanager_common-VDT1.6.1x86_rhas_4-7 with LCG change
vdt_globus_jobmanager_condor VDT1.6.1x86_rhas_4_LCG-1 vdt_globus_jobmanager_condor-VDT1.6.1x86_rhas_4_LCG-1.i386.rpm vdt_globus_jobmanager_condor-VDT1.6.1x86_rhas_4-7 with LCG enhancements
vdt_globus_jobmanager_lsf VDT1.6.1x86_rhas_4_LCG-1 vdt_globus_jobmanager_lsf-VDT1.6.1x86_rhas_4_LCG-1.i386.rpm vdt_globus_jobmanager_lsf-VDT1.6.1x86_rhas_4-7 with LCG enhancements
vdt_globus_jobmanager_pbs VDT1.6.1x86_rhas_4_LCG-1 vdt_globus_jobmanager_pbs-VDT1.6.1x86_rhas_4_LCG-1.i386.rpm vdt_globus_jobmanager_pbs-VDT1.6.1x86_rhas_4-7 with LCG enhancements
vdt_globus_rm_essentials VDT1.6.1x86_rhas_4-7 vdt_globus_rm_essentials-VDT1.6.1x86_rhas_4-7.i386.rpm Virtual Data Toolkit
vdt_globus_rm_server VDT1.6.1x86_rhas_4_LCG-1 vdt_globus_rm_server-VDT1.6.1x86_rhas_4_LCG-1.i386.rpm vdt_globus_rm_server-VDT1.6.1x86_rhas_4-7 with LCG enhancements

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Service must be restarted.

How to apply the fix

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