Description

SGE upgrade. It mainly fixes a security issue identified by the GSVG. Please, check the following information for more details on how to apply this upgrade:

1) All the SGE yaim modules were enhanced to "NOT OVERWRITE" site admin SGE configurations and break some site administrator tuning. Yaim will properly log this feature and warn the site administrator that some default configurations will be created in /tmp, which could be manually uploaded "à posteriori" (if this is really what the site admin wants to do). Since only the glite-yaim-sge-utils module is distributed with the gLite stack, the glite-yaim-sge-client and glite-yaim-sge-server components must be downloaded directly from ETICS repositories. Check https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide310#The_SGE_batch_system for further details.

2) This patch fixes a vulnerability (see advisory at http://www.gridpp.ac.uk/gsvg/advisories/advisory-43233.txt). However, because of previous point 1), the administrator SGE configurations will not be overwritten (if they exist). If you do not want to delete your present SGE settings, and you want to ensure that the security fix is in place, please run "qconf -mq <queue_name>" manually (after running yaim) on any administrator SGE host, and include the following line in your SGE cluster queues definition:

Fixed bugs

Updated rpms

The RPMs can be updated using yum via

• via apt: yum update
• or via a download from:
  
  http://glitesoft.cern.ch/EGEE/gLite/R3.1/glite-SGE_utils/sl4/i386/RPMS.updates/

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)