Updates, limitations, and known problems

Documentation updates, limitations, and known problems are documented as individual technotes in the support knowledge base at https://www.ibm.com/support/fixcentral. As problems are discovered and resolved, IBM® Software Support updates the knowledge base. By searching the knowledge base, you can find workarounds or solutions to problems.

Updates
After you install or upgrade IBM Spectrum LSF Suite for Workgroups, use IBM Fix Central to find and download the fixes that are recommended by IBM Support for LSF products. From Fix Central, you can search, select, order, and download fix packs and interim fixes for your system with a choice of delivery options.
Before you download a fix from IBM Fix Central (www.ibm.com/support/fixcentral), have the following information at hand:
  • Know your IBMid and password. You must log in to the Fix Central website before you can download a fix.
  • If you know exactly which fix you need, you can search for it directly from the Search Fix Central field on the IBM Fix Central website.
Limitations and known problems
At the time of publication, the following issues were known:
  • IBM Spectrum LSF Suite for Workgroups Fix Pack 15 does not support Logstash with IBM Spectrum LSF on SUSE Linux.
  • IBM Spectrum LSF Suite for Workgroups Fix Pack 15 cannot be deployed on RHEL 9.2 on POWER10 because of systemd issues.
  • With Fix Pack 14, you cannot enable Logstash by defining the LOGSTASH_TOP parameter in the lsf-config.yml file, if any of your LSF management, or LSF server hosts are on SUSE Linux Enterprise Server (SLES).
  • Fix Pack 10 now supports Ansible 2.9. If you have installed IBM Spectrum LSF Suite for Workgroups using Ansible older than 2.9 and have since updated Ansible to 2.9, then you will need to update the playbook again by running the FP10 bin file in order for the playbook to function properly.
  • In Fix Pack 10, the lsfadmin user is created but no password is set, therefore, must be set manually. Other default user username and password must be reset:
    • pacamdin in the Spectrum LSF Application Center database
    • egosh default username and password (Admin/admin)
  • In Fix Pack 9, upgrading from Fix Pack 7 or Fix Pack 8 requires manual configuration for remote databases (that is, using external JDBC, where the JDBC_String is defined in lsf-config.yml).

    Execute the command:

    GRANT ALL PRIVILEGES ON pac.* to pacuser@'gui_host2' IDENTIFIED BY 'pacuser';

    where gui_host2 is the full name of the gui role machine

    In the mysql.user table, add super_priv to pacuser: 

    update mysql.user set super_priv='Y' where user='pacuser';

    Set the environment variables JDBC_USER and JDBC_PASSWORD, then run the upgrade to Fix Pack 9.

  • In Fix Pack 8, the installer for this fix pack includes a check for the latest available fix pack as well as a standalone Fix Pack query tool, queryFixPack.sh, that is included with the installer. For the check and tool to run and access Fix Central, direct internet access is necessary. Therefore, using a proxy is not supported for checking the latest available fix pack.
  • For Fix Pack 8, the PMC server does not automatically after a fresh installation on Ubuntu 18.04.

    Checking the pmcadmin list shows the PMC server is not started but pnc and explorer are started. The solution is to run pmcadmin manually to start pmc.

  • In Fix Pack 8, manual configuration is required to use an existing database

    In order to use an existing database, you must create the schema and set the JDBC_STRING. In that way, the LSF Suite installation will not destroy the database and will use the existing database setup.

  • In Fix Pack 8, when the Repository.xml file has the default path set to /home, occasionally a user cannot access their scripts under their own home directory. This can be resolved by setting the share directory to $HOME.

    When installing IBM Spectrum LSF Suite for Workgroups, set the Repository.xml file to use $HOME instead of /home

    <ShareDirectory>
    <Path>$HOME</Path>
</ShareDirectory>
  • In Fix Pack 6, on Power based system, submitting a lot of jobs to the cluster will cause Logstash to use a large amount of CPU which may cause the LSF management host to become unresponsive.

    Workaround: Decreasing pipeline.workers will limit the CPU usage of Logstash but may impact its performance.

  • Installation and operation of IBM Spectrum LSF Suite for Workgroups has a limit of 128 hosts, and supports up to 25,000 active (started and pending) jobs in the system.
  • The LSF multicluster capability is limited to only sending jobs to full LSF clusters and the LSF resource connector is not enabled.