IBM Platform Symphony 5.1 Interim Fix 240854 Readme File

Abstract

1. When a candidate master host becomes the new master host, the resource tag of some computer hosts is changed to the previous resource tag.

2. The egosh user ... command accepts special characters that can fail the Symphony authentication function.

3. When a user logs on as cluster admin, the user cannot reset the user’s account password if “Restrict User Accounts Privilege” is selected.

4. Jobs are unable to run on compute hosts since the necessary packages cannot be downloaded locally.

Description

1.       When a candidate master host becomes the new master host, the resource tag of some computer hosts is changed to the previous resource tag. This causes one of the EGO services to shut down.

2.       When the user adds new accounts by running the egosh user … command, egosh does not handle special characters, which can cause issues.

3.       When “Restrict User Accounts Privilege” is selected in the GUI, a user logged on as cluster admin cannot reset the user’s account password.

4.       When soamdeploy is downloading a service package on the compute host for a user's workload, and the compute host is reclaimed suddenly, another user cannot download its service package to the compute host. This is true even if you reopen the compute host. Jobs cannot run successfully.

This fix patch applies only to the following platform:

Linux 64-bit

Readme file for: IBM® Platform Symphony

Product/Component Release: 5.1

Update Name: Interim Fix

Fix ID: sym-5.1-build240854-jpmc

Publication date: 2 Sep 2014

Last modified date: 2 Sep 2014

Contents:

1.     List of fixes

2.     Download location

3.     Products or components affected

4.     Installation and configuration

5.     List of files

6.     Note

7.     Copyright and trademark information 

1.   List of fixes

APAR: P100630.

2.   Download Location

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

3.   Products or components affected 

Product/Component Name, Platform, Fix ID:

Platform Symphony/lim, vemkd, egosh, soamdeploy Linux 64-bit, sym-5.1-build240854-jpmc

4.   Installation and configuration

4.1          Before installation 

1.    Disable all applications and shutdown 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.    Back up the file.

Log on to each management host and back up the following files that will be replaced by this fix:

> $EGO_TOP/1.2.5/linux2.6-glibc2.3-x86_64/etc/lim

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

> $EGO_TOP/1.2.5/linux2.6-glibc2.3-x86_64/bin/egosh

Log on to each compute host and back up the following binary file that will be replaced by this patch:

> $EGO_TOP/1.2.5/linux2.6-glibc2.3-x86_64/etc/lim

> $EGO_TOP/1.2.5/linux2.6-glibc2.3-x86_64/bin/egosh

> $SOAM_HOME/5.1/linux2.6-glibc2.3-x86_64/bin/soamdeploy

 

4.2          Installation steps 

1.      Low-Risk Method

These steps have the lowest risk to production environments. The cluster can be quickly rolled back if the management host fails.

a.      For every existing management host in the cluster, add a new management host. At least one of the new management hosts must be a master candidate (that is, it must be listed in the cluster's master list).

b.      Update the new hosts with this patch and verify that they are functioning correctly.

c.      Update or remove the original management hosts.

2.      Installation Instructions

a.    To update the cluster on Linux, use the RPM upgrade option on each host in the cluster to install EGO first, then the Symphony packages.

Note:  While the same Symphony package is used for both management and compute hosts, the EGO installation is only used for management hosts.

b.    For the RPM package:

· Use RPM version 4.2.1 or later.

· Use the same prefix that was used for the initial installation.

· Use the same dbpath that was used for the initial installation.

c.     For example:  

· If the dbpath and prefix were set as follows in the previous Symphony 5.1 installations:

> rpm -ivh --dbpath /tmp/rpm --prefix /opt/platform ego-linux2.6-glibc2.3-x86_64-1.2.5-nnnnnn.rpm

> rpm -ivh --dbpath /tmp/rpm --prefix /opt/platform symphony-linux2.6-glibc2.3-x86_64-5.1.0-nnnnnn.rpm

· Then the same dbpath and prefix must be used when installing current Symphony 5.1 Fix patch.

> rpm -Uvh --dbpath /tmp/rpm --prefix /opt/platform --nopreun  --nopostun ego-linux2.6-glibc2.3-x86_64-1.2.5-240854.rpm

> rpm -Uvh --dbpath /tmp/rpm --prefix /opt/platform --nopreun  --nopostun symphony-linux2.6-glibc2.3-x86_64-5.1.0-240854.rpm

 

4.3          After installation 

1. Verify the installation.

> lim -V

Platform EGO 1.2.5.240854, Aug 07 2014

Copyright Platform Computing Inc., an IBM company, 1996-2009, 2012.

 

binary type: linux2.6-glibc2.3-x86_64

notes:

>vemkd -V

Platform EGO 1.2.5.240854, Aug 07 2014

Copyright Platform Computing Inc., an IBM company, 1996-2009, 2012.

 

binary type: linux2.6-glibc2.3-x86_64

notes:

> egosh -V

Platform EGO 1.2.5.240854, Aug 07 2014

Copyright Platform Computing Inc., an IBM company, 1996-2009, 2012.

 

binary type: linux2.6-glibc2.3-x86_64

notes:

> soamdeploy -V

Platform Symphony 5.1.0.240854, Aug  7 2014

Copyright (C) 2001-2011 Platform Computing Corporation

 

2. Start the cluster and enable the application.

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

> egosh ego start all

> soamcontrol app enable <appName>

 

4.4          Uninstallation 

1.    Disable all applications and shutdown 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.     Uninstall.

Downgrade the Symphony product using the previous RPM package. For example, to roll back a Symphony host:

> rpm -Uvh --dbpath /tmp/rpm --prefix /opt/platform --nopreun --nopostun --oldpackage symphony-linux2.6-glibc2.3-x86_64-5.1.0-nnnnnn.rpm

> rpm -Uvh --dbpath /tmp/rpm --prefix /opt/platform --nopreun –nopostun --oldpackage ego-linux2.6-glibc2.3-x86_64-1.2.5- nnnnnn.rpm

3.    Start the cluster and enable the application.

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

> egosh ego start all

> soamcontrol app enable <appName>

 

5.   List of files

 

lim

vemkd

egosh

soamdeploy

 

6.   Note

 

If the resource tag for a computer host must be changed, the host should first be removed from the cluster using the "egosh resource remove" command. The resource tag should then be changed and the host restarted.

 

7.   Copyright and trademark information

© Copyright IBM Corporation 2014

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.