gLite 3.2
glite-UI - Update to version 3.2.4-0
|
Date |
13.10.2009 |
Priority |
Normal |
Description
glite-UI, glite-VOBOX
New version of WMS UI clients
For a detailed description of the new version of the WMS clients, please check this link
Please also have a look at the list of known issues.
This update fixes various bugs. For the full list of bugs, please see list below.
Fixed bugs
Number | Description |
#17534 |
unexpected behavior of glite-wms-job-output |
#27148 |
[condor-support #2036] glite-job-list-match segmentation fault on bad JDL requirements |
#29635 |
bad error message for glite_wms.conf syntax error |
#34949 |
Ctl-C'ed submission gives funny state |
#39890 |
IPv6 bug: name resolving by WMclients broken under IPv6 (glite-wms-job-list-match broken by IPv6) |
#41294 |
IPv6 bug: non compliant name resolving function in source code (gethostbyname_ex) |
#41295 |
IPv6 bug: non compliant networking function (gethostbyaddr) |
#41310 |
[WMS] IPv6 bug: non compliant name resolving function in source code (gethostbyname) |
#41322 |
[WMS] IPv6 bug: non compliant address family type in source code (AF_INET) |
#41324 |
[WMS] IPv6 bug: various non compliant functions/data structures in the wmproxy_api.cpp file |
#47134 |
WMS UI: glite-wms-job-{delegate-proxy,submit} fail if HOME is not set |
#47677 |
WMS job submission aborts on non-existent endpoint |
#48598 |
job submission fails when first WMS tried is draining !! |
#48702 |
job-list-match fails when first WMS tried is draining |
#48806 |
[glite-wms-job-status] glite-wms-job-status gives an error on SLC5 |
#50289 |
glite-wms-job-output |
#51292 |
glite-wms-job-status does not load default configuration file |
#51293 |
glite-wms-job-status does not load LBAddresses attribute |
#51294 |
glite-wms-job-submit: ExpiryTime wrong type |
#51295 |
glite-wms-job-output: fails creating the output directory if not present |
#51296 |
glite-wms-job-info: does not recognize if a job is simple or DAG/Collection |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
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)
|
|