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

 

 

gLite 3.1

glite-UI - Update to version 3.1.38-0


Date 31.08.2009
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-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-WMS, glite-WN, lcg-CE

New version of yaim core
  • Configuration changes needed for a new version of trustmanager and util-java. These changes are included in a new function not used yet by any yaim module. The idea is that any service configuring tomcat will use this function in the future.
  • The creation of users specifying a home directory wasn't working. This is fixed now.
  • GLOBUS_TCP_PORT_RANGE is not defined for the WN and it's properly defined for the TAR UI. MYPROXY_TCP_PORT_RANGE is not defined any more.
  • YAIM checks whether fetch-crl is installed and fails otherwise.
  • groups.d/ structure is now available for all the node types.
  • gridview is configured only if it's installed.
  • The verify-proxy plugin is not present in the lcmaps configuration for gridftp.
  • /opt/edg/var/info directories for the software tags are again created by yaim.
  • New site-info.pre and .post variables:
    • BDII_ARCHIVE_SIZE: It is the number of dumps of the database to keep for debugging purposes. Default is 0.
    • BDII_BREATHE_TIME: It is the time in seconds between updates of the bdii. Default is 120.
    • BDII_PASSWD: This is the password for the LDAP database used by the bdii. Default is $(mkpasswd -s 0).
    • BDII_READ_TIMEOUT: It is the amount of time to wait until an information is assumed to have timed out. Default is 300.
    • CONFIG_GRIDMAPDIR: It enables or disables the creation of the gridmap file. If set to yes, it creates it. If set to no, it doesn't create the gridmap file. Default is yes.
    • TRUSTMANAGER_CRL_UPDATE_INTERVAL: This variable is used in the trustmanager configuration and it defines how often the X509_CERT_DIR is polled for changes in the files. It's a number followed by h,m or s time units. Default is 2h.
    • TOMCAT_HOSTCERT_LOCATION: path of the tomcat host certificate. Default is /etc/grid-security/tomcat-cert.pem.
    • TOMCAT_HOSTKEY_LOCATION: path of the tomcat host key. Default is /etc/grid-security/tomcat-key.pem.
    • TOMCAT_USER: tomcat user. Default is "tomcat".
glite-UI, glite-VOBOX, glite-WN, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool

New version of dcache and dcap clients
Upgrade solving some internal coding errors and fixing SRM client command line changes.
glite-UI, glite-VOBOX, glite-WN

New version of GFAL and lcg_util
New version containing a set of bug fixes.

New version of lcg-infosites
The new patch is solving the bug 38922 which includes the use of AccessControlBaseRule

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
 #33909 [ yaim-core ] Add configurable timeouts to the BDII
 #33936 [ YAIM ] remove JAVA_HOME definition
 #38922 lcg-infosites uses AccessControlRule instead of AccessControlBaseRule
 #40208 [ YAIM ] LCG_GFAL_INFOSYS variable is defined in two places
 #44820 [ yaim-core ] The lcg-cp parallel data transfer failed on UI_TAR installed gLite-UI 3.1 nodes
 #45269 [ yaim-core ] yaim only recognizes the groups.d dir structure for a restrict set of nodes
 #45418 [ yaim-core ] Check grid-env.sh exists if -r option is used
 #45455 GFAL BDII failover can be improved
 #46066 GFAL: allowing info discovery in site BDII (as well)
 #46194 [ yaim-core ] YAIM config_crl should check for /usr/sbin/fetch-crl
 #46369 [ yaim-core ] Remove verify-proxy from lcmaps config file for gridftp
 #48206 [ yaim-core ] YAIM defines a default for JAVA_LOCATION
 #48452 [ yaim-core ] WN should not define GLOBUS_TCP_PORT_RANGE
 #48932 [ yaim-core] output is not helpful when a conf target is wrongly stated
 #48991 [ yaim-core ] needed to change config_edgusers
 #49017 [ yaim-core ] configuration changes for new trustmanager and util-java
 #49464 [ yaim-core ] configure gridview only if it's installed
 #49575 [ yaim-core ] MYPROXY_TCP_PORT_RANGE can be deleted
 #49803 [ glite-yaim-core ] objectClass 'GlueTop' not allowed
 #49831 [ yaim-core ] /opt/edg/var/info should still be created by YAIM
 #50439 lcg-cp --checksum local -> SE fails
 #50548 [LCG_UTILS] lcg-rf does not output the guid on success
 #50735 [ yaim-core ] queue_GROUP_ENABLE fails for "/vo" FQAN
 #52476 Swig error message with Python 2.5 on SL5
 #52485 lcg-cp fails to copy to gsiftp TURL
 #52545 [GFAL] wrong errno value and return code for gfal_unlink
 #52645 code of error EFAULT is wrong
 #52714 [GFAL] wrong errno value return code for gfal_chmod
 #52838 [GFAL] gfal_lseek TypeError: Expected a pointer
 #52872 [GFAL] gfal_stat errno value is wrong
 #52885 bug in config_gip_vo_tag of glite-yaim-core-4.0.7-9
 #52893 [GFAL] gfal_ls errno value is wrong
 #53122 [GFAL] gfal_pin() - result file status = 1 (instead of 0) after successful request

Updated rpms

Name Version Full RPM name Description
GFAL-client 1.11.8-1.slc4 GFAL-client-1.11.8-1.slc4.i386.rpm org.glite.data.gfal v1.11.8-1
dcache-dcap 1.9.3-0 dcache-dcap-1.9.3-0.sl4.i586.rpm dCache Client
dcache-srmclient 1.9.2-4 dcache-srmclient-1.9.2-4.noarch.rpm dCache Client
glite-UI 3.1.38-0 glite-UI-3.1.38-0.i386.rpm gLite metapackage (glite-UI)
glite-yaim-core 4.0.8-7 glite-yaim-core-4.0.8-7.noarch.rpm YAIM core package
lcg-infosites 2.6.8-2 lcg-infosites-2.6.8-2.noarch.rpm lcg-infosites
lcg_util 1.7.6-1.slc4 lcg_util-1.7.6-1.slc4.i386.rpm org.glite.data.dm-util v1.7.6-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)