Description

glite-AMGA_oracle, glite-AMGA_postgres, glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LB, glite-LFC_mysql glite-LFC_oracle, glite-MON, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

• Warnings and errors are now counted. If there are errors in the download or verification process for one or more CRLs, the exit status will be 1; if there are errors in the local setup or in the script invocation, the exit status will be 2.
• The installed CRLs no longer have the textual representation of the CRL, but only the PEM data blob, thus reducing IO and memory requirements.
• the CRL aging threshold is now set by default to 24 hours. The previous default was 0. The CRL aging threshold is set in the config file using CRL_AGING_THRESHOLD=<xx>, or with the "-a" command-line argument.
• Default network timeouts reduced to 10 seconds (was 30) and retries to 2.
• Added caching and conditional downloading. When CACHEDIR is set, the original downloads are preserved and wget timestamping mode enabled. When the content did not change, only the timestamp on the installed CRL is updated. If SLOPPYCRLHASHES is set, the has is calculated based on the name of the crl_url file, otherwise it is taken from the CRL itself.
• The CACHEDIR must be exclusively writable by the user running fetch-crl.
• Setting CACHEDIR significantly reduced the bandwidth used by fetch-crl.
• Added RESETPATHMODE setting in sysconfig. It defines whether or not to set re-set $PATH to "/bin:/usr/bin" before start. The search for OpenSSL may be done based on the old path. yes=always replace; searchopenssl=search for openssl first and then reset; no=keep original path, whatever that me be (may be empty if called from cron) Default="yes". This replaces the hard-coded path in the tool!
• Hidden "FORCE_OVERWRITE" option now has a regular name. This is backwards-compatible. Set FORCE_OVERWRITE=yes if you want files overwritten that have a CRL-like name and ought to have CRL content, but currently do not.

lcg-CE, cream-CE

Following a requirement of the WN Working Group, the new lcg-info-dynamic-software GIP plugin now supports an additional method to load software tags for SubClusters. Software tags can now be configured in:

• in /opt/glite/var/info/<vo>/<vo>.list (old method)
• in a per-SubCluster list /opt/glite/var/info/<SubCluster>/<vo>/<vo>.list (new and recommended method).

Note: For clean installations of cream CE and lcg CE, or when adding a new VO: YAIM creates /opt/glite/var/info/<SubCluster>/<vo>/<vo>.list and, due to bug 49831, /opt/edg/var/info/<vo>/<vo>.list is no longer created. It will be created again in the upcoming yaim-core 4.0.8-7 release. For a workaround see known issues pages of lcg CE and cream CE.

• tags configured in /opt/edg/var/info/<VO> are added to all SubClusters.
• tags configured in /opt/glite/var/info/<SubCluster>/<vo> Are added to the particular subclusters.

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-CREAM/sl4/i386/RPMS.updates/

Service reconfiguration after update

Not needed.

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)