gLite > gLite 3.1 > glite-UI > Update to glite-UI 3.1.15-0  
 
 

 

 

gLite 3.1

glite-UI - Update to version 3.1.15-0


Date 09.06.08
Priority Normal

Description

VOMS

voms-admin
The new voms-admin release updates voms-admin interface documentation and improves voms-admin client online documentation as well as introduces the VOMS-Admin User's guide.

Additionally, old ACL interface methods have been deprecated and several bugs have been fixed.

lcg-info

The new version of lcg-info adds the following features:
  • $LCG_GFAL_INFOSYS can now contain a comma-separated list of BDII endpoints
  • slightly improved error messages and option parsing
  • the assumption that a GlueSubCluster has the same name of its parent SubCluster is not present anymore
  • the --vo <vo> can be expressed with the VO:<vo> and VOMS:<FQAN> syntax
  • added several Glue attributes for GlueCE and GlueSubCluster
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
 #32231 lcg-info assumes that GlueClusterName and GlueSubCluster name are equal
 #34112 VOMS-ADMIN: "--upgrade" option of voms-admin-configure does not work
 #34200 voms-admin cli not failure resilent
 #34201 voms-admin web interface does not show users when adding acl entry
 #34612 VOMS-ADMIN: Internal Server Error when editing ACE

Updated rpms

Name Version Full RPM name Description
glite-UI 3.1.15-0 glite-UI-3.1.15-0.i386.rpm gLite metapackage (glite-UI)
glite-security-voms-admin-client 2.0.7-1 glite-security-voms-admin-client-2.0.7-1.noarch.rpm gLite VOMS Admin service - client package
glite-security-voms-admin-interface 2.0.2-1 glite-security-voms-admin-interface-2.0.2-1.noarch.rpm gLite VOMS Admin service - wsdl interface package
lcg-info 1.11.4-1 lcg-info-1.11.4-1.noarch.rpm lcg-info_R_1_11_4_1

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)