Readme File for IBM® Spectrum Symphony Interim Fix 528616

Readme file for: IBM Spectrum Symphony

Product Release: 7.2.1

Update Name: Interim Fix 528616

Fix ID: sym-7.2.1-build528616-pimco

Publication date: September 18, 2019

When you dynamically provision cloud hosts through HostFactory in IBM Spectrum Symphony 7.2.1.1, allocated hosts are terminated, causing tasks to be reclaimed. This interim fix provides a resolution for the issue.

Contents

1. List of fixes

2. Download location

3. Product and components affected

4. Installation and configuration

5. Uninstallation

6. List of files

7. Product notifications

8. Copyright and trademark information

1.    List of fixes

APAR: P103182, P103189, P103206

2.    Download location

Download interim fix 528616 from the following location: https://www.ibm.com/eserver/support/fixes/

3.    Product and components affected

Component name, Platform, Fix ID:

EGO, Linux x86_64, sym-7.2.1-build528616-pimco

4.    Installation and configuration

Follow these instructions to download and install this interim fix on Linux management hosts in your cluster.

System requirements

Linux x86_64 hosts

     Prerequisites

Fix Pack 7.2.1.1 (fix ID sym-7.2.1-build507069) must be installed in your 7.2.1 cluster.

Installation

a.     Log on to the master host as the cluster administrator:

> egosh user logon -u Admin

b.     Source the host environment:

(bash) > . $EGO_TOP/profile.platform

(csh) > source $EGO_TOP/cshrc.platform

c.     Stop the HostFactory service:

> egosh service stop HostFactory

d.     On each management host, create a directory (for example, /symfixes) and download the egocore-3.7.0_x86_64_build528616.tar.gz package to the directory.

e.     Use the egoinstallfixes command to install the egocore-3.7.0_x86_64_build528616.tar.gz package:

> egoinstallfixes /symfixes/egocore-3.7.0_x86_64_build528616.tar.gz --silent

NOTE: The egoinstallfixes command automatically backs up the current binary files to a fix backup directory for recovery purposes. Do not delete this backup directory; you will need it if you want to recover the original files.

f.       Launch your web browser, clear the browser cache, and log in to the cluster management console as usual.

g.     Use the pversions command to verify the installation:

> pversions -b 528616

h.     If you use requestors other than symA (for example, symB), overwrite the requestor script with the updated symA script:

> cp $EGO_TOP/3.7/hostfactory/requestors/symA/script/Main.py $EGO_TOP/3.7/hostfactory/requestors/symB/script/Main.py

i.       From the master host, start the HostFactory service:

> egosh service start HostFactory

NOTE: The symA requestor acts as a silo requestor, with its allocated resources dedicated to its configured applications. If symA’s applications are idle, resources are returned without waiting for applications configured in other requestors to finish their workloads even if those workloads are using those resources. To make symA wait for workloads by other requestors’ applications to finish before returning resources, check the return policy used by symA in the symAreq_config.json file at $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/symA/conf/, then set that policy’s return_idle_only parameter to true in the symAreq_policy_config.json file. The return_idle_only parameter specifies whether to return only idle hosts. Valid values are true or false (default). When this parameter is set to true, only hosts without any allocations are returned.

5.    Uninstallation

If required, follow these instructions to uninstall this interim fix on Linux management hosts in your cluster.

a.     Log on to the cluster management console as the cluster administrator and ensure that no provisioning requests or provisioning tasks are in progress for the symA requestor:

·       Go to Resources > Cloud > Hosts and make sure that no hosts in the Provisioned status show for the symA requestor.

·       Go to Resources > Cloud > Requests and make sure that no requests in the Created or Running status show for the symA requestor.

b.     Log on to the master host as the cluster administrator:

> egosh user logon -u Admin -x Admin

c.     Source the host environment:

(bash) > . $EGO_TOP/profile.platform

(csh) > source $EGO_TOP/cshrc.platform

d.     Stop the HostFactory service:

> egosh service stop HostFactory

e.     Log on to each management host and roll back this interim fix:

> egoinstallfixes -r 528616

f.       For each requestor other than symA (for example, symB), overwrite the requestor script with the original symA script:

> cp $EGO_TOP/3.7/hostfactory/requestors/symA/script/Main.py $EGO_TOP/3.7/hostfactory/requestors/symB/script/Main.py

g.     Launch your web browser and clear the browser cache.

h.     From the master host, start the HostFactory service:

> egosh service start HostFactory

6.    List of files

$EGO_TOP/3.7/hostfactory/requestors/symA/scripts/Main.py

7.    Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes. 

8.    Copyright and trademark information

© Copyright IBM Corporation 2019

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.