gLite 3.1
glite-WMS - Update to version 3.1.27-0
|
Date |
16.03.2010 |
Priority |
Normal |
Description
glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CONDOR_utils, glite-CREAM, glite-FTA_oracle, glite-FTM, glite-FTS_oracle, glite-HYDRA_mysql, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-LSF_utils, glite-MON, glite-MPI_utils, glite-PX, glite-SCAS, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-SGE_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE
The LB patch introduces a new version of glite-version.
glite-WMS
New version of WMS
This patch is meant to bring final touches to consolidating
current functionality for admins and users.
gLite 3.1 Update 62 requires a workaround when a glite-WMS node type is configured on a 64-bit machine. For more information see the known issues page.
This update fixes various bugs. For the full list of bugs, please see list below.
Fixed bugs
Number | Description |
#35770 |
Wrong parsing of the LB events which contains the string ending with '' in field DG.USERTAG.VALUE |
#48163 |
interlogger files may grow indefinitely |
#48635 |
WMProxy logs garbage to syslog |
#53106 |
Inefficient ICE's database access |
#53223 |
Proxy renewal of ICE should be enhanced |
#53502 |
Using sqlite database transaction instead of "old" ICE's mutex. |
#53714 |
WMS PURGER SHOULD NOT directly FORCE PURGE OF jobs when its DN is not authorized on LB server |
#55237 |
WMS job wrapper first customization point should be moved |
#55290 |
ICE's delegation renewal needs several enhancements. |
#55329 |
BAD delegation ID generation in ICE |
#55482 |
LB server version not published correctly |
#55606 |
glite-wms-job-listmatch is sometimes slow |
#55709 |
problems with glite-wms-wm restart in WMS 3.2 |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Service must be restarted.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|