gLite 3.0
glite-WN - Update to version 3.0.24-0
This update fixes various bugs. For the full list of bugs, please see list below.
This release contains a new version of YAIM. YAIM 3.1.1 will configure gLite 3.0 and gLite 3.1 services and clients. The main feature of the new YAIM is its modularity. There will be a yaim core module, a yaim client module and different yaim modules for each gLite service. In the first release not all the services have been splitted in a new module and therefore they are part of yaim core. The idea for upcoming releases is to have a full modular version.
The first YAIM 3.1.1 release is a merge of yaim 3.0.1-22 and yaim 3.1.0 (for UI and WN). The new yaim will allow to configure all gLite 3.0 and gLite 3.1 services and clients.
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration of the nodes.
Update to prevent unnecessary load on the schema (co-hosted with the registry) when the R-GMA command line tool starts up.
Bug fix release. Especially, this release includes support for VO names up to 255 characters.
glite-WN - Update to version 3.0.24-0
| Date | 16.08.07 |
|---|---|
| Priority | Normal |
Description
This update fixes various bugs. For the full list of bugs, please see list below.
YAIM
This release contains a new version of YAIM. YAIM 3.1.1 will configure gLite 3.0 and gLite 3.1 services and clients. The main feature of the new YAIM is its modularity. There will be a yaim core module, a yaim client module and different yaim modules for each gLite service. In the first release not all the services have been splitted in a new module and therefore they are part of yaim core. The idea for upcoming releases is to have a full modular version.
The first YAIM 3.1.1 release is a merge of yaim 3.0.1-22 and yaim 3.1.0 (for UI and WN). The new yaim will allow to configure all gLite 3.0 and gLite 3.1 services and clients.
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration of the nodes.
Information system (MON-Box)
Update to prevent unnecessary load on the schema (co-hosted with the registry) when the R-GMA command line tool starts up.
Data Management
Bug fix release. Especially, this release includes support for VO names up to 255 characters.
- glite-data-gfal
- Fixed behaviour of gfal_chmod (only supported with LFC)
- Fixed several segmentation fault in SRMv2.2 support
- Fixed bug #27536: GFAL access of root files on dCache SE
- Fixed a bug on SRMv2 directory creation
- Fixed bug #27226: [GFAL] can't open ClassicSE SURL
- Fixed bug #26984: lcg-cr doesn't create directory ... [with SRMv2.2]
- Extend maximum VO name length to 255
- Add easy-to-change variable for max length of VO name
- Fixed bug #26820: Wrong error (file name too long)
- Add list support for most of se_*, srm_* and srmv2_* functions
- Clean up some obsolete internal functions
- Add better error messages (with the concerning hostname/argument)
- Fixed bug #23999: GFAL doesn't cope with castor-2...
- Update of general GFAL man page.
- LCG_GFAL_VO is no more needed for gfal_open on new SURL
- Fixed bug #18104: lcg-cp only uses the first replica
- Don't force anymore to specify VO with when not needed
- glite-data-dm-util
- Fixed GGus ticket #22930: problem with the number of characters for a VO name in lcg-cr
- Installing the lcg_util library into 'lib64' instead of 'lib' on x86_64.
- Updated man pages
- Fixed option parsing of lcg-rep command line
- Don't force anymore to specify VO when not needed
- Fixed GGUS ticket #20086: lcg-uf - return code
Fixed bugs
| Number | Description |
|---|---|
| #18104 | lcg-cp only uses the first replica |
| #23999 | GFAL doesn't cope with castor-2 file names |
| #26820 | Wrong error (file name too long) |
| #26983 | VO name too long |
| #26984 | lcg-cr doesn't create directory of the day under generated in DPM with space token specified |
| #27226 | [GFAL] can't open ClassicSE SURL |
| #27504 | CLI submits a call to getAllTables when initialised |
| #27536 | GFAL access of root files on dCache SE |
| #27841 | strange node type problem with at least WN_torque |
Updated rpms
| Name | Version | Full RPM name | Description |
|---|---|---|---|
| GFAL-client | 1.9.3-1 | GFAL-client-1.9.3-1.i386.rpm | Grid File Access Library |
| glite-rgma-command-line | 5.0.5-1 | glite-rgma-command-line-5.0.5-1.noarch.rpm | R-GMA command line |
| glite-WN | 3.0.24-0 | glite-WN-3.0.24-0.noarch.rpm | gLite Worker Node |
| glite-yaim-clients | 3.1.1-8 | glite-yaim-clients-3.1.1-8.noarch.rpm | org.glite.yaim.clients |
| glite-yaim-core | 3.1.1-8 | glite-yaim-core-3.1.1-8.noarch.rpm | org.glite.yaim.core |
| lcg_util | 1.5.2-1 | lcg_util-1.5.2-1.i386.rpm | LCG utilities |
The RPMs can be updated using apt via
- via apt: apt-get dist-upgrade
- or via a download from:
http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.updates/
Service reconfiguration after update
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration of the nodes.
Service restart after update
None.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)