gLite 3.1
glite-WMS - Update to version 3.1.14-0
|
Date |
08.04.2009 |
Priority |
Normal |
Description
glite UI, glite-WMS
Upgrade of CREAM and CEmon clients. The main changes are:
- Problem involved with staging of InputSandbox files fixed.
- It is now possible to use the CREAM client even if the relevant VO VOMS cert file is not installed in the clients, as requested by OSG.
- Support for some problems reported in IPv6
- Fixed some problems which prevented the build on sl5_x86_84
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 |
#41227 |
IPv6 bug: non compliant name resolving function in source code (gethostbyname) |
#41253 |
IPv6 bug: non compliant address casting function in source code |
#41255 |
IPv6 bug: non compliant networking function (gethostbyaddr) |
#41268 |
IPv6 bug: non compliant address data in source code (sockaddr_in) |
#41269 |
IPv6 bug: non compliant networking function (gethostbyaddr) |
#41274 |
IPv6 bug: non compliant address casting function in source code (inet_aton) |
#41275 |
IPv6 bug: non compliant address casting function in source code (inet_aton) |
#44184 |
cream-cli: different commands, same "<command> -h" help/usage outputs |
#44188 |
cream-cli: `glite-ce-* -d`: gives not correct output if "BAD" GLITE_CREAM_CLIENT_CONFIG used |
#44454 |
InputSandbox files modified on creamCE (bad symbols added) |
#45334 |
lack of an option to turn off the AC signature verify in VOMSWrapper |
#46134 |
bad warnings and errors from glite-ce-delegate-proxy on missing VOMS cert |
#46405 |
VOMSWrapper should try more than once to open a proxy file |
#47458 |
There's a BAD handling of credentials taken to the gsoap-plugin |
#47460 |
There's a BAD handling of credentials taken to the gsoap-plugin |
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)
|
|