gLite 3.0
lcg-CE - Update to version 3.0.8-0
This update fixes various bugs. For the full list of bugs, please see list below.
lcg-vomscerts v. 4.3.0 provides the new host certificate for voms.cern.ch in addition to the current certificate that will expire on Jan. 9 2007. The expired certificate for lcg-voms.cern.ch has been removed.
lcg-CE - Update to version 3.0.8-0
| Date | 19.12.06 |
|---|---|
| Priority | High |
Description
This update fixes various bugs. For the full list of bugs, please see list below.
lcg-vomscerts v. 4.3.0 provides the new host certificate for voms.cern.ch in addition to the current certificate that will expire on Jan. 9 2007. The expired certificate for lcg-voms.cern.ch has been removed.
Fixed bugs
| Number | Description |
|---|---|
| #15298 | cleanup-grid-accounts.sh does not consider GPFS as non-local filesystem |
| #16534 | TORQUE_server node in YAIM |
| #16855 | config_mkgridmap in a glitece+torque_server create gridmapfile via edg-mkgridmap |
| #19120 | config_mkgridmap creates edg-mkgridmap cron job on gliteCE |
| #21057 | FTS: sometimes transfer-url-copy doesn't call PutDone after a transfer failure |
| #21058 | FTS: transfer-url-copy reports 'No such active transfer' for successfully completed transfers |
| #21209 | There is a possible vulnerability with VO boxes |
| #21296 | FTS: web-service locks up several times a week under high load |
Updated rpms
| Name | Version | Full RPM name | Description |
|---|---|---|---|
| cleanup-grid-accounts | 1.0.2-1 | cleanup-grid-accounts-1.0.2-1.noarch.rpm | cleanup grid accounts |
| glite-yaim | 3.0.0-34 | glite-yaim-3.0.0-34.noarch.rpm | glite-yaim |
| lcg-CE | 3.0.8-0 | lcg-CE-3.0.8-0.noarch.rpm | LCG CE node |
| lcg-vomscerts | 4.3.0-1 | lcg-vomscerts-4.3.0-1.noarch.rpm | VOMS server certificates for LCG VOs |
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
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)