Lists of servers and chassis are incorrect after user credentials change - IBM System x, BladeCenter, Flex System



Source

RETAIN tip: H21700

Symptom

Configuration Patterns does not function properly after the authorization status of the user account is changed.

Such changes include the account becoming locked, the password expiring, and the password being changed. Resolving the authorization issue does not fix Configuration Patterns. The time it takes after such a change for symptoms to appear varies. Symptoms include the following:

  • When attempting to deploy a server pattern or profile, the list of servers to deploy to contains no real servers; it may contain placeholder servers.
  • When attempting to create a new server pattern from an existing server, the list of existing servers to choose from is unexpectedly empty.
  • When attempting to deploy a chassis pattern or profile, the list of chassis to deploy to contains no real chassis; it may contain placeholder chassis.
  • When attempting to create a new chassis pattern from an existing chassis, the list of existing chassis to choose from is unexpectedly empty.
  • When attempting to deploy a placeholder chassis to a real chassis, the list of real chassis to deploy to is unexpectedly empty.
  • When creating or editing a standby server pool, the list of servers from which to choose new standby servers is unexpectedly empty.

Affected configurations

The system is configured with at least one of the following:

  • Flex System Manager (FSM) - Configuration Patterns 1.2.0, 1.2.1

This tip is not system specific.

This tip is not option specific.

Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Please see the compatibility page for more information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/

Solution

This behavior will be corrected in a future release of IBM Flex System Manager (FSM) - Configuration Patterns distributed as part of the FSM update package.

The target date for this release is scheduled for fourth quarter 2013.

The file is or will be available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and Operating system on IBM Support's Fix Central web page, at the following URL:

Workaround

Restart the Flex System Manager (FSM). Configuration Patterns will start to use the updated account credentials and will function normally.

Additional information

A security token is cached by Configuration Patterns and is used after a successful internal call to get inventory information from FSM. Even after the credentials change, that same security token is used by Configuration Patterns, causing the internal call to fail.

Restarting the FSM causes Configuration Patterns to re-fetch credentials and use a correct security token, and function properly again. In the noted release, an FSM restart will not be required.

Applicable countries and regions

 


Document id:  MIGR-5093578
Last modified:  2013-10-15
Copyright © 2014 IBM Corporation