gLite 3.1
glite-VOBOX - Update to version 3.1.25-0
|
Date |
02.04.2009 |
Priority |
Normal |
Description
Highlights
- New service provider for VOBOX
This release contains a set of bug fixes. None of them is specially relevant for 64bit WN. Only the fact that
now 64bit libraries are properly included in the grid enviroment.- This patch adds a missing dependency,
glite-info-provider-service-1.0.3-0.noarch.rpm, into the VOBOX.- org.glite.security.lcas-lcmaps-gt4-interface
was defined as OBSOLETE in the glite-VOBOX metapackage. This has been removed.
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 |
#38236 |
[ yaim-clients ] <relocated>/glite/external/etc/grid-security/vomsdir/BUILD is used for globus devel build |
#39112 |
[ yaim-clients ] config_workload_manager_client should implement config_workload_manager_client _check |
#39693 |
[ yaim-clients ] YAIM version for yaim clients |
#39939 |
[ yaim-clients ] Remove NSAddresses from glite_wmsui.conf |
#40199 |
[ yaim-clients ] Clean variables in glite-vobox.pre |
#40563 |
[ yaim-clients ] config_gip_service_release should be included in the VOBOX |
#40575 |
[ yaim-clients ] Implement config_info_service_vobox |
#40654 |
[ yaim-clients ] Variable cleaning |
#40732 |
[ yaim-clients ] WN needs config_vomses |
#40944 |
[ yaim-clients ] 64bit TAR_WN is missing /usr/lib64 in LD_LIBRARY_PATH |
#41494 |
[ yaim-clients ] OUTPUT_STORAGE is not created by yaim during UI configuration |
#43603 |
[ yaim-clients ] Service Discovery needs to be disabled on the WMS UI configuration. |
#43881 |
[ yaim-clients ] yaim module config_wn screws up python path |
#47672 |
VOBOX should depend on glite-info-provider-service rpm |
#47846 |
glite-VOBOX fails to install due to glite-security-lcas-lcmaps-gt4-interface |
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)
|
|