gLite 3.0
glite-BDII - Update to version 3.0.2-2
This update fixes various bugs. For the full list of bugs, please see list below.
This yaim release completes the BDII_site and CE separation. It also contains the VOBOX password fix and various other bugfixes. Bug 21609 is however not fixed.
To configure lcg-CE with site BDII the following command should be issued:
configure_node site-info.def CE BDII_site
Please pay attention to the known issues.
glite-BDII - Update to version 3.0.2-2
| Date | 19.12.06 |
|---|---|
| Priority | High |
Description
This update fixes various bugs. For the full list of bugs, please see list below.
This yaim release completes the BDII_site and CE separation. It also contains the VOBOX password fix and various other bugfixes. Bug 21609 is however not fixed.
To configure lcg-CE with site BDII the following command should be issued:
configure_node site-info.def CE BDII_site
Please pay attention to the known issues.
Fixed bugs
| Number | Description |
|---|---|
| #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 |
|---|---|---|---|
| glite-BDII | 3.0.2-2 | glite-BDII-3.0.2-2.noarch.rpm | gLite BDII node |
| glite-yaim | 3.0.0-34 | glite-yaim-3.0.0-34.noarch.rpm | glite-yaim |
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)

