Known Issues for glite-CLUSTER

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.

YAIM does not warn about missing CE_HOST_xxx_QUEUES

Description

The variable CE_HOST_<ce name>_QUEUES should be set in the yaim cluster configuration file, but if it is missing yaim does not give a warning or error.

Only one subcluster allowed per cluster

Description

There should only be one subcluster defined per cluster. This is currently a restriction needed for correct operation of the workload management system.

Cluster and subcluster Unique IDs restrictions

The cluster and subcluster Unique IDs, set with:

CLUSTER_<cluster-identifier>_CLUSTER_UniqueID

SUBCLUSTER_<subcluster-identifier>_SUBCLUSTER_UniqueID

must not contain upper case letters, i.e. they may contain only lower case alpha numeric characters and any of the three characters '.', '_' and '-'. The unique IDs must be globally unique, for instance base it on the DNS domain to ensure it will not collide with an ID at another site. However, the cluster Unique ID do not have to be unique with respect to subcluster Unique IDs. e.g. currently a cluster will only have one subcluster and the subcluster UniqueID may be the same as the cluster UniqueID.

Issue when reconfiguring so that a subcluster ID is removed

There is a known issue when reconfiguring a glite-CLUSTER so that a subcluster ID is removed from the configuration. (e.g. a subcluster is completely removed or the subcluster's UniqueID is changed): Directories with the name of the old subcluster Unique IDs are not removed and need to be removed manually from the glite-CLUSTER node or they will continue to be published:

cd $GLITE_LOCATION/var/info

rm -rf old_subcluster_name

where <old_subcluster_name> is the UniqueID of any subcluster which is no longer defined.

YAIM known issues

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