Home

Know Issues with UniCluster 4.1

The most up to date list of issues with UniCluster 4.1 can be found on the Bugzilla page. The following issues were present at the time of release and are considered more user affecting than the other ones:

  • Cannot enable ARCo SGE component on a node other than the main node. - While not impossible to do through a couple manual steps the current SGE ARCo component will not work if it isn't installed on the same node as the SGE main component.
  • Cannot enable ARCo SGE component at the same time as the main component. - If the ARCo component is enabled at the same time as the main component it may not install properly.
  • Some directories are assumed to be empty at the time of installation - Several directories in /var/www/html (yum,cfm,images,kickstart,kits,repos), /opt/tortuga, and /etc/cfm are assumed to not exist on the system at time of install. If there are files or directories at these location you may have issues.
  • Grid Kit Compute component can fail on Installer node - If the Installer node has public and private interfaces and its hostname contains the public DNS suffix the Grid kit compute component will not install correctly due to the use of the private DNS suffix in the hostname added to the Grid kit configuration.
  • Grid Kit Scheduler Event Generator Broke - The SGE Scheduler event generator for SGE is broke due to changes in SGE 6.2 that aren't compatible with the verison of the SEG bundled with UniCluster 3.2.