IBM Platform Symphony 6.1.1 Interim Fix 417722 Readme File

Abstract

When a hybrid scheduling policy is used for a resource plan, a consumer that has not selected hybrid owned slots is mistakenly allocated slots if the sibling consumer demands slots.

Description

With a hybrid scheduling policy, consumers that do not have hybrid owned slots selected (that is, consumers that do not have Owned Slots under Model type: Hybrid selected on the Resource Plan page within the management console), do not deserve slots.

However, when the consumer’s sibling consumer selects hybrid owned slots and configures the slot value to 0, and the sibling consumer demands slots, the consumer is also given slots, if there are free slots available. Eventually, the consumer’s allocated slots are reclaimed since it should not get any slots.

For a Platform Symphony application with this consumer scenario, SSM successfully starts but is then quickly ended. SD then reports errors in the logs.

With this fix, vemkd will not allocate slots to the consumer and no reclaim will happen.

This interim fix applies only to the following platform:

Linux2.6-glibc2.3-x86_64

Readme file for: IBM® Platform Symphony

Product/Component Release: 6.1.1

Update Name: Interim Fix 417722

Fix ID: sym6.1.1-build417722

Publication date: 17 August 2016

Last modified date: 17 August 2016

Contents:

1. List of fixes

2. Download location

3. Products or components affected

4. Installation and configuration

5. List of files

6. Copyright and trademark information

1. List of fixes

APAR: P101855

2. Download location

Download Interim Fix 417722 from the following location: http://www.ibm.com/eserver/support/fixes/.

3. Products or components affected

Product/Component Name, Platform, Fix ID:

Platform Symphony/VEMKD Linux 64-bit, sym6.1.1-build417722

4. Installation and configuration

4.1 Before installation

1. Shut down the cluster.

Log on to the host as the cluster administrator and run:

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown all

2. Back up the affected files.

Log on to all hosts in the cluster, and back up the following file that will be replaced by this fix:

$EGO_TOP/1.2.8/linux2.6-glibc2.3-x86_64/etc/vemkd

4.2 Installation steps

Log on to all hosts in the cluster, and replace the old files with the downloaded package:

> tar zxfo sym6.1.1_lnx26-lib23-x64_build417722.tar.gz -C $EGO_TOP

4.3 After installation

Start the cluster.

Log on to the master host as the cluster administrator and run:

> egosh ego start all

> soamcontrol app enable <appName>

4.4 Uninstallation

1. Shut down the cluster.

Log on to the master host as the cluster administrator and run:

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown all

2. Restore the backup file.

Log on to all hosts and restore the backed up file:

$EGO_TOP/1.2.8/linux2.6-glibc2.3-x86_64/etc/vemkd

3. Start the cluster.

Log on to the master host as the cluster administrator and run:

> egosh ego start all

> soamcontrol app enable <appName>

5. List of files

$EGO_TOP/1.2.8/linux2.6-glibc2.3-x86_64/etc/vemkd

6. Copyright and trademark information

© Copyright IBM Corporation 2016

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.