UMD-1 UMD-1.0.0

UMD1.0 Release Notes

Additional details Any additional information that does not fit other categories should be put here.

Installation Notes Please collate for the Installation Notes all the issues and workarounds detected in Verification and StagedRollout, separate for each product. Please do not summarise and link to the reports, but give detailed instructions here (even if repeated from the reports). If applicable, provide the GGUS links here, too.

Known issues Similar to the Installation Notes, please collate detected issues and workarounds coming from Verification and StagedRollout, separate for each product. Again, please duplicate the information here, and provide links to GGUS tickets if applicable.

Change Log A list of products that is included in this release.

EMI-UI sl5 x86_64

• Additional Details:
• Installation Notes: Extra repository EMI.extras.sl5.x86_64 is required for UI installation.
• Known Issues:
  • before using lcg-* commands users must export CSEC_NOTHREAD:

#export CSEC_NOTHREAD=1

• • dCache clients (srm* commands) need to use Oracle/Sun JDK. Oracle/Sun JDK is the default java installed on the node.
  • LCG_GFAL_INFOSYS does not support a list of topBDIIs
    • GGUS Ticket: https://ggus.eu/tech/ticket_show.php?ticket=72196
    • Workaround is to use only 1 topBDII host:

# $export LCG_GFAL_INFOSYS=TOP_BDII_HOST>:<PORT>

• Change Log:

EMI-APEL sl5 x86_64

• Additional Details:
• Installation Notes: Mysql server must be installed and Mysql root passwd must be set before yaim configuration:

#yum install mysql-server
#service mysqld start
#chkconfig --level 345 mysqld on
#Mysqladmin –u root password ‘<a-good-password>’

• Known Issues:
  • Problems publishing data to central apel server:
  • GGUS ticket: https://ggus.eu/ws/ticket_info.php?ticket=71814
  • Workaround is to change the timeout to a higher number: in /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml. By default, it is set to 30 minutes (1800000 milliseconds), extending it, for example, to 7200000.
• Change Log:

EMI-ARGUS sl5 x86_64

• Additional Details:
• Installation Notes:
  • In case of reinstallation, save your policy in a file to be loaded later with “pap-admin apf”. In case policy cache stands for a while, once policies are loaded don’t forgot to reload policies and clear pdp cache responses with:

/etc/init.d/argus-pdp reloadpolicy
/etc/init.d/argus-pepd clearcache 

• • YAIM function for a minimal working configuration (based on traditional CE authorization config) does not exist yet.
  • Workaround: a script was proposed http://wwwae.ciemat.es/~delgadop/from-groupmap-to-policy.sh
  • Added to a deployment twiki: https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment
• Known Issues:
  • The PAP authorization configuration parser does not support kerberized style DN like, "/DC=country/DC=DC/O=organization/CN=host/host_name". GGUS ticket: https://ggus.eu/dmsu/dmsu_ticket.php?ticket=69841.
  • The common EMI XACML profile is not yet finalize, and not yet implemented by Argus.
  • Argus does not encode hyphens in gridmapdir links as CEs: https://ggus.org/tech/ticket_show.php?ticket=71547
  • Argus encoding of roles/groups in gridmapdir links differs from that of CEs: https://ggus.org/tech/ticket_show.php?ticket=71548
  • Argus does not update time of gridmapdir links: https://ggus.org/tech/ticket_show.php?ticket=71550
  • Argus NRPE restart commands hard-code erroneous init.d scripts: https://ggus.org/tech/ticket_show.php?ticket=72328
• Change Log:

EMI-bdii-site sl5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-bdii-top sl5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
  • GLUE2EndpointImplementationVersion: yaim
    • It is incorrect when querying the Glue2 resource info
• Change Log:

EMI-CREAM sl5 x86_64

• Additional Details:
  • New yaim variable USE_ARGUS If the value for this variable is yes, ARGUS is used as authorization system for the CREAM CE. If instead the value for this variable is no, the old authorization systems (i.e. gJAF, LCAS, LCMAPS) are used.
• Installation Notes: MYSQL_PASSWORD variable is a mandatory for yaim cream configuration.
• Known Issues: http://grid.pd.infn.it/cream/field.php?n=Main.KnownIssues
• Change Log:

EMI-CLUSTER SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-lsf_utils SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
  • Cosmetic Issue: Dynamyc info lsf uninitialized value on an EMI Cream-CE. GGUS: https://ggus.eu/ws/ticket_info.php?ticket=71613.
  • In /var/log/bdii/bdii-update.log displays this "warning" (Use of uninitialized value in concatenation (.) or string at /usr/bin/glite-info-dynamic-lsf line 1027 (#1)). To suppress this warning assign a defined value to your variables.
• Change Log:

EMI-torque_utils SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-torque_client SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-torque_server SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-dgas SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-dpm SL5 x86_64

• Additional Details:
• Installation Notes:
  • Correct metapackage is:

yum install emi-dpm_mysql

• • VO default dirs are not created: An issue was found into /etc/cron.monthly/create-default-dirs-DPM.sh script. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=71357. LCG_LOCATION variable is not defined and the script fails to find DPM binaries. To solve this issue DPM administrators MUST define LCG_LOCATION inside create-default-dirs-DPM.sh. As example:

LCG_LOCATION=/usr

• • In a fresh install mysql server must be installed before yaim configuration.
  • In a fresh install /etc/cron.monthly/create-default-dirs-DPM.sh MUST be executed after yaim configuration.
  • SL 5.6 uses user and group ids which cause conflicts with those in /opt/glite/yaim/examples/edgusers.conf (e. g. group avahi-autoipd:x:156: conflicts with group infosys ):
  • Workaround is to use a different edgusers.conf (set variable EDGUSERS in site-info.def)
• Known Issues:
  • After yaim runs manually set “chkconfig bdii on” and “chkconfig ldap on”
• Change Log:

EMI-glexec_wn SL5 x86_64

• Additional Details:
• Installation Notes:
  • Run ldconfig after each update, as the packages don't seem to do this by themselves.
  • All services are recommended to be restarted. gLExec is an exception, as it is not a service.
  • Glexec yaim plugin contains syntax errors: GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71569
  • When trying to run the yaim configuration for glexec wn, yaim complains with the following error: /opt/glite/yaim/bin/../defaults/glite-glexec_wn.post: line 66: unexpected EOF while looking for matching `"' /opt/glite/yaim/bin/../defaults/glite-glexec_wn.post: line 77: syntax error: unexpected end of file.
    • This issue can be easily fixed using a patch: https://ggus.org/pages/windownload.php?attid=ATT7716
• Known Issues:
  • This version of C-PEP needs to be tested more on root-squashed environments.
  • The verify-proxy plugins fails to verify Terena eScience Personal certificate chains deeper then 5 certificates. 5 is ok, 6 is not.
• Change Log:

EMI-lb SL5 x86_64

• Additional Details:
• Installation Notes:
  • Job registration has been proven to work correctly with an EMI WMS and a glite3.2 WMS.
  • bdii is not started by default by gLite services must be started by hand after yaim configuration. GGUS ticket:https://ggus.eu/tech/ticket_show.php?ticket=71448
    • use /sbin/service bdii restart to start bdii service correctly after yaim conf.
• Known Issues:
  • Due to faulty DNS over IPv6 resolution in the c-ares library (v. 1.6.0), L&B does not work in most scenarios involving IPv6-only machines. Upgrade c-ares to 1.7.3 and relaunch yaim to get full IPv6 functionality.
• Change Log:

EMI-voms_mysql SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
  • The VO AUPs (for example https://<VOMS_HOST>:8443/voms/<VO>/aup/load.action) aren't shown because voms-admin is still pointing to a path that doesn't exist any more: /var/glite/etc/voms-admin/<VO>/vo-aup.txt..
    • the workaround proposed for the AUP problem is to update the table.

mysql> select * from aup_version;
mysql> update aup_version set url="file:/etc/voms-admin/<VO>/vo-aup.txt" where url="file:/var/glite/etc/voms-admin/<VO>/vo-aup.txt"; 
             

• Change Log:

EMI-WN SL5 x86_64

• Additional Details:
• Installation Notes:
  • Python-ldap package missing:
    • GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71167
    • Python-ldap package is missing, therefore WN probes are not executable.
    • Workaround: Installing python-ldap and openldap-clients is enough for WN probes:

yum install python-ldap opendlap-clients

• Known Issues:
  • dcache client tools fail with java errors.
    • GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71198
    • Using SUN's JDK instead of gcj solves the issue.
    • Configure the default java version to use, e.g:

#update-alternatives --install /usr/bin/java java /usr/java/default/bin/java 2000 --slave /usr/bin/keytool keytool /usr/java/default/bin/keytool --slave /usr/bin/rmiregistry rmiregistry /usr/java/default/bin/rmiregistry --slave /usr/lib/jvm/jre jre /usr/java/default/jre

• • WN does not pass org.sam.WN-SoftVer test:
    • GUS ticket:https://ggus.eu/ws/ticket_info.php?ticket=71723
    • No workaround at the moment: waiting for SAM Update-12.
• Change Log:

EMI-unicore-gateway SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-client SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-hila SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
  • Hila Shell doesn't write log files, messages are displayed directly in the command line.
• Change Log:

EMI-unicore-xuudb SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-uvos SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-ws SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-tsi SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log:

EMI-proxyrenewal SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
  • It is worth noting that MyProxy in its standard setup generates usage statistics and sends that information to MyProxy developers (outside the scope of EMI).
• Change Log:

EMI-ARGUS-EES SL5 x86_64

• Additional Details: This package is included into ARGUS product. Read ARGUS release notes for further information.
• Installation Notes:
• Known Issues:
• Change Log:

EMI-unicore-registry SL5 x86_64

• Additional Details:
• Installation Notes:
• Known Issues:
• Change Log: