Known Issues for glite-CREAM

Only the known issues for gLite 3.2 have been migrated. Please check the old 3.1 known issues page if you don't find the solution here.

Need to exclude taking c-ares from slc5-updates 3.2 sl5_x86_64 (Tracker Url)

Release of CREAM CE 1.6.4 uses c-ares 1.3.0-4. In particular it will not be possible to update/install the node to c-ares 1.6 due to unsatisfied dependencies. In case you have the slc5-updates repository enabled, which contains c-ares 1.6, c-ares will need to excluded e.g.

Update:

  • Excluding when running the yum update command: yum update --exclude=c-ares
  • Adding an exclude line to the .repo file, e.g. in /etc/yum.repos.d/slc5-updates.repo exclude=c-ares

Clean Install:

  • Adding an exclude line to the .repo file, e.g. in /etc/yum.repos.d/slc5-updates.repo exclude=c-ares

This known issue is also valid for the main SL5 repository in SL5.6, the same workaround can be applied on the main sl5 repository. 

Central list of known issues 3.2 sl5_x86_64

For a complete list of issues see: http://grid.pd.infn.it/cream/field.php?n=Main.KnownIssues

Installation known issue with Tomcat 3.2 sl5_x86_64

Description

Due to a dependency problem within the Tomcat distribution in SL5, follow the installation steps explained below:

  • first install xml-commons-apis: yum install xml-commons-apis
  • then install CREAM yum install glite-CREAM

/opt/edg/var/info/$VO is not created in CREAM 3.2 clean installations 3.2 sl5_x86_64 (Tracker Url)

Description

Due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.

The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:

mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info

where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.

 

Do not move the directories named <subcluster> from /opt/glite/var/info.

YAIM known issues

For an up to date documentation on configuration known issues, please check also the YAIM known issues page.