HP SERVER AUTOMATION RELEASE NOTES

 

Software version: 9.05

Original publication date: September 2011

Server Automation release notes contain information for users who are familiar with the installation and maintenance of Server Automation, Storage Visibility and Automation, SE Connector, Application Deployment Manager, DMA integration, and SA-OO integration. The notes contain information that is not included in books or online Help.

In addition, these release notes contain:

DOCUMENTATION NOTES:

Content

You can find information about the following in this document:

New in This Release

Installation

Known Issues

Fixed Issues for This Release

New in Previous Releases

Fixed Issues for Previous 9.0x Releases

Documentation Errata

HP Software Support

Legal Notices

    

The sections contain information that is not included in books or online Help.

The primary audience for these release notes are users who are familiar with the installation and maintenance of Server Automation, Storage Visibility and Automation, SE Connector, Application Deployment Manager, DMA integration, and SA-OO integration.


----------------------------------------------------------------------------------------------------------------------------------------------------------

New In This Release

The following features are new for 9.05.

Qualified Managed Platforms (9.05)

For more support and compatibility information, download the HP Server Automation Support and Compatibility Matrix for this release from the HP Software Support Online web site at:
www.hp.com/go/hpsoftwaresupport.

This release provides qualified managed platform server support for the following platforms:

Application Deployment Manager (9.05)

 

Automatically Created Directories

For a Configuration File component, the application designer can now instruct the Application Deployment Manager to create the destination directory if it does not yet exist on the target server.

Partial Import/Export

The admtool utility now supports importing and exporting one or more specific applications. You can specify the list of applications to be imported or exported on the command line, or you can specify a CSV file that contains the list of applications. In both cases, the names of the applications must be separated by semicolons (for example: app1;app2;app3).

New admtool Option

Purpose

--exportAppList <list>

Export a list of applications specified on the command line.

--exportAppListFile <file>

Export a list of applications specified in a CSV file.

--importAppList <list>

Import a list of applications specified on the command line.

--importAppListFile <file>

Import a list of applications specified in a CSV file.

Example 1: Export Three Specific Applications

/opt/opsware/da/bin/admtool.sh -e --exportAppList "app1;app2;app3" --exportFile ADM_export.xml
/opt/opsware/da/bin/admtool.sh -e --exportAppListFile app_list.csv --exportFile ADM_export.xml

Example 2: Import Three Specific Applications

/opt/opsware/da/bin/admtool.sh -i --importAppList "app1;app2;app3" --importFile ADM_import.xml
/opt/opsware/da/bin/admtool.sh -i --importAppListFile app_list.csv --importFile ADM_import.xml

Example 3: Preview the Import of Three Specific Applications
/opt/opsware/da/bin/admtool.sh -p --importAppList "app1;app2;app3" --importFile ADM_import.xml
/opt/opsware/da/bin/admtool.sh -p --importAppListFile app_list.csv --importFile ADM_import.xml

Sample contents of the app_list.csv file:

app1;app2;app3;

Audit and Remediation (9.05)

In this release, you can specify the execution order for custom script audit rules. In the SA Client, in the Rules > Custom Scripts view, you can move selected audit rules up or down to specify the execution order. The audit rules are saved in the order you specify. This order displays when you open the audit or audit policy.

The execution order for remediation is not separately specified. Instead, remediation for selected, non-compliant rules are executed in the same order that is defined in the audit or audit policy. For example, if the audit policy has 10 rules and rules 2, 4, 6, and 8 are non-compliant, and rules 4 and 8 are selected for remediation, rule 4's remediation script will run first, followed by rule 8's remediation script.

 

Localization (9.05)

This release adds support for Windows Server 2008 R2 (IA64) in Japanese.

 

SA-OO Integration (9.05)

 

Integrating the OO SDK Client Certificate

The SA-OO Integration feature is not available until you import the required OO SDK Client Certificate into SA. SA 9.05 is bundled with two OO SDK certificates that apply to different OO versions, as shown in the following table. Before you import the certificate into SA, make sure it is compatible with your OO version.

OO SDK Certificate

OO Version

oocert2007

OO 7.5x, 7.6x, 9.0
oocert2011

OO 9.02.0002 or later

To integrate the new certificate, you must perform the steps in the procedure detailed below.

Note: If your architecture includes a master core and one or more secondary cores, follow the steps in this section for the master core and for each of the secondary cores. Similarly, if your SA computer has a sliced-core installation with one or more slices, repeat the steps for each slice.

Integrating the OO SDK Client Certificate

To integrate the certificate:

  1. Stop the Web Services Data Access Engine (Twist):

    /etc/init.d/opsware-sas stop twist

  2. Transfer the OO Certificate to SA (when you are prompted for a password for the next steps, use: changeit)
    1. Export the OO Central Certificate:
      /opt/opsware/jdk1.6/jre/bin/keytool -exportcert -alias oocert2011 -file /tmp/oocentral.crt -keystore /var/opt/opsware/twist/oocert

      Connect to the previous version of OO that still uses the older certificate, which expired May, 2011 (optional):
      /opt/opsware/jdk1.6/jre/bin/keytool -exportcert -alias oocert2007 -file /tmp/oocentral.crt -keystore /var/opt/opsware/twist/oocert

      Note: The keystore /var/opt/opsware/twist/oocert contains the following certificates:
      oocert2007 - OO certificate bundled with OO versions 7.5, 7.6, and 9.0, valid until May, 2011
      oocert2011 - OO certificate bundled with OO 9.02.0002 and later, also released as part of the OO hotfix #132914, valid until July, 2016
      pas - OO certificate that is the same as oocert2007, retained for backward compatibility
    2. Import the OO Central Certificate to the SA Java Runtime Environment (JRE) keystore:
      /opt/opsware/jdk1.6/jre/bin/keytool -importcert -alias oocert -file /tmp/oocentral.crt -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts

      Note: Any alias can be used when importing the certificate, as long as it is not already used in that keystore. The sample command above uses oocert, but you can use any other name.

 

OO-SA Integration Updates (9.05)

Updates pertaining specifically to the OO-SA integration (Server Automation operations performed within Operations Orchestration) are delivered through the HP Live Network at https://www.www2.hp.com/.

 

Operating Systems and Platforms Supported/Deprecated (9.05)

For support and compatibility information for Server Automation Cores, Agents, clients, and Satellites, see the Server Automation Support and Compatibility Matrix for this release.

For a list of supported operating systems and platforms for Storage Visibility and Automation Managed Servers, SE Connector, SAN Arrays, Fibre Channel Adapters, SAN Switches, File System Software, Database Support, and Storage Essentials Compatibility, see the Storage Visibility and Automation Support and Compatibility Matrix .

To download the matrices and to check for updates to these documents, go to the HP Software Support Online web site at: www.hp.com/go/hpsoftwaresupport.

The HP Software Support Online web site requires that you register for an HP Passport and sign in. To register for an HP Passport, select the New users - please register link on the HP Passport login page.

Support for SLES 11 for zSeries

The SLES 11 for zSeries platform is supported in SA 9.05 with the functionality that existed in 9.03. However, the platform is not supported for new 9.04 or 9.05 features.

Support for Operating System Sequence

SA 9.05 provides support for OS Sequence based provisioning of servers that have duplicate MAC addresses in different networks. The following restrictions apply:

Note: Provisioning servers with duplicate MAC addresses in the same network is not supported.

See also the Known Issues section of these release notes (QCCR1D 136445 and 136592).

 

Configuration and System Requirements (9.05)

For configuration and system requirements information for Server Automation, download the SA 9.0 Simple/Advanced Installation Guide and the SA 9.0 Upgrade Guide from the HP Software Support Online web site at: www.hp.com/go/hpsoftwaresupport.

You can also find feature-specific configurations in the New in This Release section of these release notes.

 

Enhanced Red Hat Linux Itanium 64-bit Network Image Boot Menu (9.05)

As of the SA 9.05 release, the HP Itanium 64-bit image bootloader menu has been enhanced. After booting the SA-provided Itanium 64-bit boot image, you will see the following screen:

                               HP IA64 Bootloader

Please choose a boot image :

   > linux           - Linux 3 Build Agent
   > linux-txt       - Linux 3 Build Agent for serial consoles.
   > linux           - Linux 5 Build Agent
   > linux-txt       - Linux 5 Build Agent for serial consoles.
   > winpe           - Windows Build Agent (WINPE IA64)
   > exit            - Exit
  
In this screen:

As with previous releases, the Itanium 64-bit OS Provisioning process is the same as the Linux OS Provisioning process described in the SA 9.0 User Guide: Application Automation, Chapter 11: OS Provisioning.

 

Remediation Scalability Enhancements (9.05)

In 9.05, remediation performance and scalability have been significantly enhanced.

There are two key areas of improvement:

Two new components were introduced to the Slice Component bundle:

To benefit from this enhancement, you must apply the 9.05 patch to each SA Server Agent on each SA Managed Server in the facility.


Note: This enhancement applies only to agents that communicate directly with a Linux-based SA core. You must upgrade your agents to the agent version shipped with the 9.05 patch to benefit from this enhancement. You can continue to use non-upgraded agents, but they will not benefit from this enhancement. See the SA 9.0 User’s Guide: Server Automation for information about the Agent Upgrade Tool.

The component services are integrated with the global Start script and are started with the other services. In particular, tsunami and memcached are started with the Slice component bundle components. A new log directory is also created for the tsunami logs:  /var/log/opsware/tsunami

Note: For information about component log files or starting and stopping individual components, see the SA 9.0 Administration Guide.

Performance Considerations

For best results when deploying and using the remediation performance and scalability enhancements in this release, be aware of the following considerations.

Package Locality

When packages are uploaded to an SA core, the packages are associated with the core/facility (locality) in which they were uploaded. When you remediate a software policy against a specific managed host, it attempts to fetch the package from its local software repository or software repository cache.

If the package or packages in question do not reside in the local software repository, the local software repository attempts to fetch the package from the remote software repository where the package is. The package is then served to the managed host by proxy. Depending on the network speeds between cores, this operation can result in a performance penalty that would affect the remediation job.

Recommendation: To achieve the highest levels of performance, you should turn on Software Repository Replication for your mesh. Software Repository Replication was introduced in SA 9.0 and ensures that packages are replicated between cores in the same mesh automatically and frequently, which eliminates the performance overhead associated with proxying remote packages.

Satellite Performance

The initial release of this enhancement includes core-side improvements only. This means that machines reporting to a core via a satellite will not directly benefit from this enhancement. For Satellites that share a local LAN with a core machine (e.g. those used for HA or security boundaries), it is possible to disable the Software Repository Cache component via a customization of your satellite Agent Gateway configurations.

Recommendation: Contact HP Software Professional Services for more information on customizing Agent Gateway configurations.

 

Upgrades (9.05)

Customized Settings

If you have customized settings, such as Java heap settings, you must reapply your customizations after you install 9.05, as the settings are set to the SA default during installation or upgrade.

Server Agent

After you upgrade to SA 9.05, you should upgrade the Server Agent on each Managed Server in the facility. The latest version of the Server Agent enables you to use new SA features. You can continue to use non-upgraded Agents, you will not be able to take advantage of all SA 9.10 functionality. See the SA User’s Guide: Server Automation for information about the Agent Upgrade Tool.

Changes to the solpatch_import.conf file

Due to Oracle's acquisition of Sun Microsystems, if you were previously accessing the SunSolve website and you migrated your Sun account to an Oracle account instead, your solpatch_import.conf file is out of date and must be updated to reflect that change.

To update your solpatch_import.conf file:

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Installation

This section describes the Server Automation installation procedure for this patch.

As with previous SA releases, all SA Core installations and upgrades must be performed
by HP Professional Services or HP-certified consultants. SA Satellite installations and
upgrades performed by customers continue to be supported.

General Information

Script Running Order

The pre-patch, database update and patch install scripts must be run in the following order:

SA Script Running Order - Upgrade Table

Upgrade From

To

Script Running Order

9.0

9.05
  1. patch_database.sh
  2. patch_opsware.sh
  3. patch_contents.sh
9.01 9.05
  1. patch_opsware.sh
  2. patch_contents.sh

9.02

9.05
  1. patch_opsware.sh
  2. patch_contents.sh
9.03 9.05
  1. patch_opsware.sh
  2. patch_contents.sh
9.04 9.05
  1. patch_opsware.sh
  2. patch_contents.sh

SA Script Running Order - Rollback Table

Rollback From

To

Script Running Order

9.05

9.0
  1. patch_opsware.sh
  2. patch_database.sh

 

 

Database Schema Update Procedure

Required only if you have not previously applied the SA 9.01 patch. The script run
during this procedure makes required changes to the Model Repository including adding
required tables and objects. Perform the following tasks to install database updates:

  1. Before running the patch install script, perform steps below to ensure that the script
    20_truth_modify_truth_stats_job_90.sh is run during patch installation.

    This script modifies the TRUTH database users dba_job that collects schema statistics.

    Note: This is an optional script that fixes issues described in QCR1D: 93757.
    This script is run by the patch install script, patch_database.sh , only when
    you have made the following changes.

    1. Create the file:

      /var/opt/opsware/OPSWpatch_sql/optional_updates.conf

      on the server on which you will run the patch install script, patch_database.sh .
    2. Edit optional_updates.conf and add this entry:

      truth_modify_truth_stats_job=1

      When you run the patch install script patch_database.sh , it checks for the
      existence of optional_updates.conf, and if the file exists and contains the entry
      specified in step b, it runs the script 20_truth_modify_truth_stats_job_90.sh
      which then modifies the dba_job that collects schema statistics.

      If optional_updates.conf is not found, or if the
      truth_modify_truth_stats_job=1 entry is not found in the file, then the script
      20_truth_modify_truth_stats_job_90.sh will not be run.
  2. Mount the SA 9.05 distribution. Invoke patch_database.sh on the Model Repository host:

      <distro>/opsware_installer/patch_database.sh --verbose -r <response file>

      Where <response file> is the response file last used to install/upgrade the system.

      Usage: patch_database.sh [--verbose] -r <response file>

      patch_database.sh automatically detects if a database update is already
      installed and presents a corresponding menu:

    1. If the database update has not been previously applied, you see
      the following:
      Welcome to the Opsware Installer.
      It appears that you do not have a database update
      installed on this system.
      Press 'i' to proceed with patch installation.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: i
    2. Enter i at the prompt to begin the database update.
    3. If the database update has previously been applied, you see
      the following:

      Welcome to the Opsware Installer.
      It appears that you have installed or attempted
      to install a previous version of the database
      update on this system.
      Press 'u' to upgrade the patch to the current version.
      Press 'r' to remove this patch.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: u
      You chose to upgrade the patch. Continue? [y/n]: y

      Enter u at the prompt then Y to begin the database update.

  3. After you make your selection, the installer completes the new (or interrupted) installation.
    On completion, you see a screen similar to the following:

    [timestamp] Done with component Opsware SQL patches.

    [timestamp] ########################################################

    [timestamp] Opsware Installer ran successfully.

    [timestamp] ########################################################

Note: After running the patch_database.sh script, you may see the following error when running
the System Diagnostic test on your core:

Test Name: Model Repository Schema
Description: Verifies that the Data Access Engine's version of the schema matches
the Model Repository's version.
Component device: Data Access Engine (spin)
Test Results: The following tables differ between the Data Access Engine and the
Model Repository: local_data_centers, role_class_bridge.

This error is invalid and you can disregard it.

Upgrading from SA 7.8x to SA 9.05

When upgrading an SA Multimaster Mesh from 7.8x to 9.05, the %opsware_patch_sql entry is NOT removed from the secondary Model Repository server inventory file when it should be removed. This procedure will rectify this problem.

Perform the following tasks before upgrading from 7.8x to 9.05:

1) From the 9.05 distribution media, copy the following file:

<distro>/ opsware_installer/conf.opsware_37/truth_mm_slave.conf

to the 7.8x secondary Model Repository host in the following location:

/var/opt/opsware/install_opsware/conf/truth_mm_slave.conf

Note: Alternatively, you can  add the following line to the /var/opt/opsware/install_opsware/conf/truth_mm_slave.conf file on the 7.8x secondary core Model Repository host under the %prereqs section:

opsware_patch_sql

2) Upgrade all cores in the 7.8x Multimaster Mesh to SA 9.0 and ensure that opsware_patch_sql has been removed from secondary Model Repository host’s inventory file.

The inventory file is located here:

/var/opt/opsware/install_opsware/inv/install.inv

3) Upgrade to 9.05 by following the instructions below.

Patch Installation Procedure

Note: Before performing the tasks in this section ensure that you have completed the
tasks listed in Database Schema Update Procedure.

Perform the following tasks to install SA 9.05:

  1. Mount the SA 9.05 distribution. Invoke patch_opsware.sh on every host in the
    core/satellite facility:

    <distro>/opsware_installer/patch_opsware.sh --verbose

    Usage : patch_opsware.sh [--verbose]

    patch_opsware.sh automatically detects whether or not there is a patch
    already installed and presents a corresponding menu:

    1. Non-upgraded System : If your system has not been upgraded,
      you see the following menu:
      Welcome to the Opsware Installer. It appears that
      you do not have any patches installed on this system.
      Press 'i' to proceed with patch installation.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: i

      Enter i at the prompt to begin the installation.

    2. Previously Upgraded System : If an SA patch has already been installed
      successfully, when patch_opsware.sh is invoked from a newer patch
      release, you see the following menu:
      Welcome to the Opsware Installer. It appears that you have
      installed or attempted to install a previous version of
      the patch on this system.
      Press 'u' to upgrade the patch to the current version.
      Press 'r' to remove this patch.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: u

      Enter u at the prompt to begin the upgrade.

  2. After you make your selection, the installer completes the new (or interrupted)
    installation.

The installer displays the following upon completion:

[<timestamp>] Done with component Opsware Patch.

[<timestamp>]

########################################################

[<timestamp>] Opsware Installer ran successfully.[<timestamp>]

########################################################

Software Repository Content Upgrade

This section details upgrades to the software repository content on the upload
distribution (such as agent packages to be reconciled to managed servers).

General Information

 Note: Unlike core patches, Software Repository content upgrades cannot be rolled back.

Upgrading the First Core Content

  1. On the First Core Software Repository store ( word store ) host, invoke the upgrade
    script:

    <distro>/opsware_installer/patch_contents.sh --verbose -r <response file>

    where <response file> is the response file last used to install/upgrade the SA Core.

    The following menu is displayed:

    Welcome to the Opsware Installer. Please select the components
    to install.
    1 ( ) Software Repository - Content (install once per mesh)
    Enter a component number to toggle ('a' for all, 'n' for none).
    When ready, press 'c' to continue, or 'q' to quit.

    Enter either 1 or a and press c to begin the installation.

  2. If the Software Repository content image is not installed on the server, the following
    message will be displayed:

    [<timestamp>] There are no components to upgrade.
    [<timestamp>] Exiting Opsware Installer.

Rolling Back the Patch

To rollback SA 9.05 to SA 9.0, invoke the script:

<distro>/opsware_installer/patch_opsware.sh --verbose

If this is a patched system, the following will be displayed:

Welcome to the Opsware Installer. It appears that you have previously
completed installation of this patch on this system.
Press 'r' to remove this patch.
Press 's' to show patch contents.
Press 'q' to quit.
Selection:

Enter r at the prompt to remove the patch.

Notes:

Rolling Back the Database Schema Update

Note: If you created the optional file
/var/opt/opsware/OPSWpatch_sql/optional_updates.conf
with the entry truth_modify_truth_stats_job=1 (modifies the TRUTH database
users dba_job that collects schema statistics.) during the install process as described
in Step 1 of the Database Schema Update Procedure, you must ensure that the same
optional_updates.conf file is available during the rollback process.

To roll back the database schema update, enter this command:

<distro>/opsware_installer/patch_database.sh --verbose -r <response file>

Where <response file> is the response file last used to install/upgrade the system.

If the database has been updated, you see the following:

Welcome to the Opsware Installer. It appears that you have previously
completed the installation of this database update on this system.
Press 'r' to remove this patch.
Press 's' to show patch contents.
Press 'q' to quit.
Selection: r

Enter r at the prompt to begin the database schema update rollback.

Server Agent

After you upgrade to SA 9.05, you should upgrade the Server Agent on each Managed Server in the facility. The latest version of the Server Agent enables you to use new SA features. You can continue to use non-upgraded Agents, you will not be able to take advantage of all SA 9.05 functionality. See the SA User’s Guide: Server Automation for information about the Agent Upgrade Tool.

 

Post Patch-Installation Tasks

Windows Server 2008 R2 x64

This section describes how to set up SA support for Windows Server 2008 R2 x64.

NOTE: Required only if you have not set up SA support for Windows Server 2008 R2 x64
when (and if) you applied the SA 9.01 patch.

SA 9.01 and later provide improved support for
Windows Server 2008 R2 x64. Windows Server 2008 R2 x64 now appears with its own
entries in the SA Client rather than as a subset of Windows Server 2008.

However, there are some tasks you must perform in order to migrate any Software Policies,
Application Configurations, packages (units), Patch Policies and/or OS Provisioning objects
you may already have set up for your server(s).

Migrating Software Policies, Application Configurations and/or Patch Policies is handled by
running a script, windows_2008_R2_fix_script.pyc , provided with SA 9.01 and later
in the directory:

<distro>/opsware_installer/tools

The script is called windows_2008_R2_fix_script.pyc and is invoked as follows:

/opt/opsware/bin/python2 windows_2008_R2_fix_script.pyc [--mrl=<MRL_ID>|--listmrls|--help

 Note 1:

Note 2:

 It is very important that you ensure that the MRL(s) specified when you invoke this migration script are correct. Once the script is invoked, migration begins immediately.
Providing the incorrect information when invoking this script can cause irreversible data
integrity errors.

The script has the following options:

Script Options Table

Options

Description

--listmrls, -l

List all Windows Server 2008 x64 MRLs (ID, Name and Media Path)

--MRL=<MRL ID>

Migrate the MRL with the specified ID to the Windows Server 2008 R2 x64 platform.
Can be specified multiple times.

--help, -h

Display usage and help

Note: Migrated objects other than Patch Policies are not copied, they are attached to the new
Windows Server 2008 R2 x64 configuration.

For Patch Policies, Windows Server 2008 R2 x64 copies are created of Windows Server 2008 x64
Patch Policies containing R2 patches (x64 patch library).

The Windows Server 2008 x64 Patch Policies are then detached from the Windows Server 2008 R2 x64
servers and the equivalent Windows Server 2008 R2 x64 Patch Policy copies are attached to the
Windows Server 2008 R2 x64 servers.

Note: You can run windows_2008_R2_fix_script.pyc multiple times without issue. The changes
made by the script cannot be rolled back.

If a Windows Server 2008 x64 R2 server is in an unreachable state after the migration script is run,
data errors may cause the server to appear in the Mismatched Server Platform list.

To resolve the mismatch error, do the following:

  1. Bring the server to MANAGED state.
  2. Run hardware registration on the server.

 

Requirements

Software Policies

After migration completes, the Software Policy appears in the SA Client Navigation
pane under Library/By Type/Software Policies/Windows/Windows Server 2008 R2 x64
and Windows Server 2008 x64.

During migration, Software Policies are modified only if:

When processing policy items, the script looks for the following types of objects:

If the script finds a policy item that has Windows Server 2008 x64 in the platform list it
will migrate that policy item to Windows Server 2008 R2 x64.

The order of items in the Software Policy is retained and remediation status remains
unchanged.

If the script identifies an existing Software Policy as a Windows Server 2008 R2 x64 policy,
it does not modify it during processing.

Packages

The script migrates only the packages that have Windows Server 2008 x64 in the platform
list and are included as policy item inside a Software Policy that is migrated by the script.

After migration, the package will appear in the SA Client under both the
Windows Server 2008 x64 and Windows Server 2008 R2 x64 folders in
Library/By Type/Packages/Windows.

The script does not take into account the package type. It looks for packages included in
migrated Software Policies that are attached to Windows Server 2008 x64. Server Module
Result objects, Windows Registry objects and Windows Services objects cannot be migrated
by the script because their platform associations cannot be changed.

Properties settings (including general, archived scripts, install parameters, install scripts,
uninstall parameters, uninstall scripts) are preserved.

Application Configurations

The migration script migrates an application configuration if:

During migration, the script adds Windows Server 2008 R2 x64 to the application
configuration's platform list. The script also inspects all application configurations'
associated templates (CML templates) and if a template has Windows Server 2008 x64
in the platform list it is also migrated.

There is no undo option.

Patch Policies

During migration, the script appends R2 to the Patch Policy name. For example, for a
patch policy named 2008 XYZ Policy, the migration script creates a new
Windows Server 2008 R2 x64 policy named 2008 XYZ Policy R2 if:

Note: If a Windows Server 2008 R2 x64 policy named 2008 XYZ Policy R2 already exists,
the applicable patches will be added to it.

If Windows Server 2008 R2 x64 servers, or device groups containing
Windows Server 2008 R2 x64 servers, are attached to Windows Server 2008 x64 patch
policies, the migration script will detach these policies and attach the newly created or
updated equivalent Windows Server 2008 R2 x64 policies. Applicable Patch Policy
exceptions are also migrated.

If metadata associated with Windows Server 2008 R2 x64 patches has been modified
(for example: install/uninstall flags, pre/post install/uninstall scripts), that metadata will
be migrated.

Note: In some cases, for example supplemental patches, Microsoft patches may have
more than one version with the same name which causes those patches not to be
migrated when running the migration script. In these cases, you must manually
migrate the affected patches.

WindowsImageName Custom Attribute

The specification of the WindowsImageName custom attribute with
Windows Server 2008 R2 x64 is somewhat different from other platforms.

For Windows Server 2008 R2 x64, the expected values are:

Windows Server 2008 R2 SERVERDATACENTER
Windows Server 2008 R2 SERVERDATACENTERCORE
Windows Server 2008 R2 SERVERENTERPRISE
Windows Server 2008 R2 SERVERENTERPRISECORE
Windows Server 2008 R2 SERVERSTANDARD
Windows Server 2008 R2 SERVERSTANDARDCORE
Windows Server 2008 R2 SERVERWEB
Windows Server 2008 R2 SERVERWEBCORE

The populate-opsware-update-library Script

A new option, --no_w2k8r2, is provided for the populate-opsware-update-library
script and is used to specify that Windows Server 2008 R2 x64 patch binaries should
not be uploaded. For more information about the populate-opsware-update-library
script, see the SA User's Guide: Application Automation .

Windows Server CLI Installation

If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after
upgrade to SA 9.05, you must update the Agent on that server to the latest version. Errors
occur during OCLI installation on Windows servers with earlier Agent versions.

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Known Issues

This section describes known issues for 9.0 through 9.05. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.

Known Issues for This Release


QCCR1D Symptom/Description Platform Subsystem Workaround

Agent

QCCR1D100660 Windows ADT login fails for administrators
that are not user Administrator due to security
controls for Windows UAC.		 Windows Server 2008 using UAC Agent Deployment

Turn off UAC:

  1. In the Control Panel, click User Accounts.
  2. In the User Accounts window, click User
    Accounts.
  3. In the User Accounts tasks window, click
    Turn User Account Control on or off.
  4. If UAC is currently configured in Admin
    Approval Mode, the User Account Control
    message appears. Click Continue.
  5. Clear the Use User Account Control (UAC)
    to help protect your computer check box,
    and then click OK.
  6. Click Restart Now to apply the change right
    away, or click Restart Later and close the
    User Accounts tasks window. After the
    workaround is performed, any user belonging
    to the Administrators group will be able to
    deploy agents.
QCCR1D107917 Failed SA agent installation returns
gencache.py error message in the agent log file (%SystemDrive%\Windows\System32\
opsware-agent-installer- .log).		 Windows Agent Installer

Remove all the files from the following three directories,
if they exist, and reinstall the agent.

%SystemDrive%\Program Files\opsware\agent\lcpython15
\Lib\site-packages\win32c om\gen_py\

%TEMP%\gen_py

%SystemDrive%:\Windows\temp\gen_p

QCCR1D110347

Windows servers running a pre-9.0 agent can
perform a scan on an upgraded 9.0 core but not
on a freshly installed 9.0 core because scanning
Windows utilities are retained on the upgraded
core but are absent from the freshly installed core.

 Windows Agent

Upgrade the agent on the managed servers that you registered
with SA 9.0.

 

QCCR1D111593 Agent fails to install when there is a gateway problem, but the agent log reports that the installation was successful.

Windows Agent Installer

Make sure the gateway can be reached from the managed server.

QCCR1D118437

Agent deployment fails several times due to timeout issues when the uudecode utility
is not installed on the machine to which the Agent is deployed.

Red Hat or SUSE Linux s390x Agent Deployment/Upgrade

Install the uudcode utility on the machine(s) to which Agents are to be deployed to facilitate Agent deployment.

 

QCCR1D123031

Reprovisioning for Red Hat Enterprise Linux 6 with the ext4 file system is not yet supported.

 Linux   None

Application Configuration

QCCR1D50099 Data-manipulation script that includes Japanese
characters in the filename and content fails
with errors.		 Windows Application Configuration - Backend Grant Read-Write privileges for Client Features -
Manage Installed Configuration and Backups on Servers.
QCCR1D111765 You are unable to modify Application Configuration
value sets for all scopes (Configuration, Facility,
Customers) even when you have appropriate
permissions.		 Independent Application Configuration Grant Read-Write privilege for Client Features - Manage
Installed Configuration and Backups on Servers.

Application Deployment Manager

QCCR1D113202 Application Deployment Manager fails to launch when a non-default Oracle System ID is used (SID is not “truth”). The installer should automatically add the truth.sid to the da.conf file. Independent Application Deployment Manager

To resolve the issue, perform the following steps:

  1. Stop Application Deployment Manager using the following command:

    /etc/init.d/opsware-sas stop da
  2. Add the truth.sid configuration parameter to the /etc/opt/opsware/da/da.conf file. For example:

    truth.sid=<newSIDname>
  3. Restart Application Deployment Manager service:

    /etc/init.d/opsware-sas start da
QCCR1D115187 Application Deployment Manager fails to launch after you upgrade from 7.8 to 9.0 in an Oracle Real Application Clusters (RAC) environment. Independent Application Deployment Manager

Perform the following steps after the upgrade :

  1. Run the following command to stop the Application Deployment Manager:

    /etc/init.d/opsware-sas stop da
  2. In the /etc/opt/opsware/da/da.conf file, remove the truth.sid configuration parameter. For example:

    truth.sid= <SIDname>
  3. Edit the following file:

    /opt/opsware/da/webapps/arm/WEB-INF/
    classes/hibernate.cfg.xml
  4. Locate the block that contains the connection.driver and connection.username properties.
  5. Add the following string:

    <property name="connection.url">
    jdbc:oracle:thin:@ (DESCRIPTION =
    (ADDRESS = PROTOCOL = TCP)
    (HOST = host1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)
    (HOST = host2)(PORT = 1521))
    (LOAD_BALANCE = yes) (CONNECT_DATA =
    (SERVER = DEDICATED) (SERVICE_NAME =
    truth) (FAILOVER_MODE = (TYPE = SELECT)
    (METHOD = Preconnect) (RETRIES = 180)
    (DELAY = 5))))</property>

    Here, host1 and host1 are variables that represent the names of your database servers. Include one

    (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))

    specification for every database server in your environment.
  6. Run the following command to restart the Application Deployment Manager:

    /etc/init.d/opsware-sas start da
  7. Re-run the Opsware Installer—or, alternatively, invoke the following command to populate Application Deployment Manager baseline data:

    /opt/opsware/da/bin/da_baseline.sh

APX

QCCR1D117680

APX session timeout is not correctly implemented.

 

 Independent APX

To increase timeout for Web APX Proxy (Note: this must be
done at all the Slices on all the Cores):

  1. Edit /etc/opt/opsware/apxproxy/apxproxy.conf
    to specify both the session timeout and socket
    timeout. Make sure socket timeout is at least
    equal to session timeout. For example,

    apxproxy.apx.session.timeout=1200000
    apxproxy.apx.socket.timeout=1200000

  2. Edit both /opt/opsware/apxhttpd/conf/httpd.conf.tmpl
    and /var/opt/opsware/ogfs/mnt/root/opt/opsware/
    apxhttpd/conf/httpd.conf.tmpl     to add a timeout directive.
    Add this property after the "Server" property. For example,

    imeOut 1200

    Remember, unlike apxproxy.conf, the timeout value in
    httpd.conf.tmpl is in seconds, not millisecon

  3. Restart the Core.

Audit and Remediation

QCCR1D102706 After a patch rollback, audits, patches and AppConfig,
software policies are missing from the Select
Compliance Columns dialog on an SA 7.81 Secondary
Core if the First Core is SA 7.80.		 Independent Audit and Compliance The pick lists are empty because the search to fill them relies
on a new SA 7.81 search field that is not in the database
because of the rollback. In a Multi-master mesh, HP
recommends that you patch the primary core first, followed by
secondary cores and satellites, thus ensuring that the primary
core is at a higher version (such as SA 7.81 or higher) than the
secondary cores. If you must roll back the SA 7.81 patch in a
Multi-master Mesh, HP recommends that you roll back the
secondary cores and satellites first, then the primary core.
However, if you cannot rollback a secondary core(s), you can
restore the missing data by running the following on the 7.81
secondary core(s):
/opt/opsware/bin/python2 /var/opt/opsware/
OPSWpatch/OPSWspin/scripts/ QC94469_apply.pyc

BSA Essentials Dataminer

QCCR1D112784

In multimaster environments, Application
Deployment data mismatches between SA and
BSA Essention can occurr if the data is replicated
across the Model Repository Multimaster
Component (vault) to where the BSA Essentials
Dataminer is installed within the first few
milliseconds of a minute.

 Independent BSA Essentials Dataminer None

Database Scanner for Oracle

QCCR1D88091 Database Scanner for Oracle binaries, which are
copied to a managed server during each
snapshot process, are not automatically removed.		 Independent Database Scanner for Oracle

Remove the binary files:

  1. From the Navigation pane, select Device >
    Servers > All Managed Servers    .
  2. Right-click the managed server and select
    Run Script > Select Script.
  3. In the Run Server Script window, click Select
    Script to display the Select Script dialog.
  4. In either the Browser Scripts tab or the Browse
    Folders tab, select the "post-uninstall script for
    Database scanner for Oracle [unix|win]" script
    and then click Select.
    To view this script, you must have privileges on
    the /Opsware/Tools/Server Modules
    com.opsware.server.module.storage.
    dbscanner.oracle    " folder.
  5. In the Run Server Script window, click Next.
  6. Click Start Job in the Options pane. Do not specify
    any additional parameters.
  7. When the job successfully finishes, the files
    related to the Database Scanner for Oracle
    will no longer be on the cleaned managed server.

 

 

Bug ID: 156909 / QCCR1D68263 Free space in the tablespace view does not
match what is displayed in the Oracle
Enterprise Manager (OEM) tablespace.		 Independent Database Scanner for Oracle

None

Note: There is an OEM bug about some tablespaces showing the
incorrect used size. The Database Scanner for Oracle gets the
tablespace used size directly from all of its data files, which
avoid the OEM bug.
QCCR1D91143

The status of an ASM Diskgroup shown in
the Properties view (for one database instance
only) is different than the status shown in the
Database Configuration Assistant (DBCA) view
(a CONNECTED status is displayed instead of a
MOUNTED status).

Independent Database Scanner for Oracle None

Help System

QCCR1D132631 When you click the Help button in the Agent Deploy dialog box, the help system displays a blank page. Independent Help System Use the F1 help to get information about Agent Deployment.

Installer

QCCR1D100931

Patch rollback of the SA 7.81 patch displays
a failure error:
(Failed to remove software
policy (8710001) ProtocolError:
<ProtocolError for 192.168.161.22/
cogrpc.py: 404 Not found>)

and fails to remove Storage Compliance
(which is a new feature and incompabile with
SA 7.80).

After reporting the error, rollback continues to
the next component. The rollback completes
successfully without other errors and cleans
up all patch-related files and folders on the core.

 Independent

SA Installer

 Manually remove Storage Compliance by running the following
command on one of the core servers:
/opt/opsware/bin/smtool --username=detuser
--password=<detuserpwd> --remove=com.opsware.server.
module.storage.compliance
QCCR1D114639 If you install additional Slice Component
bundle instances after patching the SA Core
to version 9.XX, wayscript versions are set to
version 9.0 rather than to the patch version.		 Independent

SA Installer

In the SA Web Client:

  1. Log in as administrator (opsware admin user) and
    navigate to Environment > Customer > Opsware >
    Custom Attributes > CORD_OPSWwayscripts    .
  2. Identify the SA core server by checking the value field
    of the custom attribute CORD_OPSWway scripts.
  3. Log in to the SA Core server you identified in step 1
    and execute the following commands:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts
    /scripts./post_after_startup.sh
  4. Apply any required hotfixes to the wayscripts.

ISM Tool

QCCR1D110511

ISM tool fails to upload ISM into a software
policy because the tool mistakenly detects
the registry key HKLM\Software\
Wow6432Nodeidentified, causing it to
identify a Windows Server 2008 server as a
Windows Server 2008 x64 server.

 Windows Server 2008 ISM Tool

If you are developing an ISM on a server that has this
registry key, temporarily rename the registry during
ISM development so that ISMtool will correctly identify
the server as a Windows Server 2008 server.

Model Repository

QCCR1D83813 Attempting to synchronize a Multimaster
Mesh conflict on a ServiceInstance fails
with the following type of error:
ERROR -- Unable to perform UPDATE!
spin.genericDatabase error:
'ORA-02291: integrity constraint (.)
violated - parent key not found
ORA-06512: at ........
(srvc_inst_id = :p3)' with args
'('20-OCT-2008 23:40:21',
'124970002', '3230002')'
 Independent Model Repository
(Truth)

Run the patch script patch_database.sh ensuring
that the file optional_updates.conf is configured as
described in Database Schema Update Procedure
in the Installation section of these release notes.

 

OCLI

QCCR1D118249

When we upload a package like this
C:\Program Files\Opsware\ocli\scripts>
oupload -O "Windows 2008" -e gb2312
--pkgtype ZIP -d "/"  c:\download\testpkg中文.zip
we get an error
SUMMARY:
Name: exceptions.UnicodeEncodeError
Description: 'ascii' codec can't encode characters
in position 7-8: ordinal not
in range(128)

 Win2008 Win2008 R2 OCLI None

OS Provisioning

QCCR1D93231

Remediation from a re-provisioning job fails because the operation times out before the remediation can occur.

 Linux OS Provisioning None
QCCR1D100928

RAID deployment fails when the RAID
configuration is captured using ACU
version 8.35.7.0 (linux5 boot image) for valid
RAID configurations on machines with SCSI
drives because the "pretty printing" of SCSI
drive bus values uses 0-based index instead
of 1-based index.

 Red Hat Enterprise Server 5 OS Provisioning
  1. Perform captures with ACU Version 8.25.5.0
    (using boot images other than linux5) and deploy
    those.
  2. Modify the raid.hpacu.script custom attribute value for
    RAID Array Configuration on ACU Version:
    8.35.7.0-captured RAID policies to use the correct drive
    indexes.
    For example, modify this captured configuration:
    ; Array Specifications
    Array= A
    ; Array Drive Type is Parallel SCSI
    ; 1:0 (36.4 GB), 1:1 (36.4 GB), 1:2 (36.4 GB),
    1:3 (36.4 GB),
    1:4 (36.4 GB), 1:5 (36.4 GB)
    Drive= 1:0, 1:1, 1:2, 1:3, 1:4, 1:5
    to the following:
    ; Array Specifications
    Array= A
    ; Array Drive Type is Parallel SCSI
    ; 2:0 (36.4 GB), 2:1 (36.4 GB), 2:2 (36.4 GB),
    2:3 (36.4 GB),
    2:4 (36.4 GB), 2:5 (36.4 GB)
    Drive= 2:0, 2:1, 2:2, 2:3, 2:4, 2:5
QCCR1D103362

After a server is provisioned using a RedHat
DHCP-LESS image in the VLAN, attempting to
reprovision the server causes the server to reboot,
after which the reprovision process fails at the
Anaconda Configure TCP/IP window, prompting
for network information.

 Independent OS Provisioning - OCC - Client None
QCCR1D103394

When booting a target server using the Linux boot CD in a DHCP-less network, specifying an IP address already in use by another host will prevent the target server from successfully registering with the SA core. No network check/warning error is displayed.

 Red Hat Linux OS Provisioning None
QCCR1D104194

When RAID deployment fails after the RAID
controller configuration has been cleared,
subsequent RAID captures or deployments
will fail unless RAID is first configured manually.

The following error displays:
Exit status: 1280

Error message from ACU: ERROR: (2821)
No controllers detected.

 Independent OS Provisioning - Backend

Manually set the RAID controller configuration:

  1. Restart the server and press F8 when prompted.
  2. Create logical drive(s).
  3. Assign physical disks and RAID level.

 

After the RAID controller has been manually configured,
SA can be used to capture and deploy RAID configurations on
the machine.

QCCR1D104739 During a network boot of the server, the following
error displays:
"No driver found" screen appears:
"Unable to find any devices of the type
needed for this installation type.
Would you like to manually select your
driver or use a driver disk? [Select driver]
[Use a driver disk] [Back]"
 Red Hat Enterprise Server IA64 OS Provisioning The missing driver is not required. Press F12 to bypass the driver.
QCCR1D109077

Assign Customer OS Build Plan content script fails if
customer names contain quote characters.

 Windows OS Provisioning Backend Specify the customer ID instead of the actual customer name.
QCCR1D110563

In some environments, when writing I18N content to
files from OGFS to WinPE, data and files that contain non-ASCII characters might be invalid.

 Windows OS Provisioning Backend Use only ASCII characters if possible.
QCCR1D111245

When you upgrade, unless you have customized the bm.reprovision_attributes_to_preserve system
configuration value, your custom values will not be
replaced by the new values required for this SA release -
instead, old values are retained.

 Independent OS Provisioning Re-enter your values by appending them to this setting
on the SA Web Client
QCCR1D111337

The Cannot access target server over OGFS
error occurs randomly on a server while running an
OS Build Plan on multiple servers.

 Solaris OS Provisioning None
QCCR1D111781

When provisioning Windows Server 2003 or 2008
using an OS Sequence to a non-C drive using a
WIM image:

  • Provisioning works for Windows Server
    2003 OS Media.
  • Provisioning fails for Windows Server
    2003 WIM and Windows Server 2008
    OS Media and WIM.
    When provisioning Windows Server 2003
    or 2008 using OS Build Plans to
    non-C drives, Windows 2003 & 2008 OS
    Media installs are supported, but Windows
    2003 & 2008 WIM installs are not supported.

 

 OS Provisioning Backend

Windows Server 2003

 None
QCCR1D114523

When performing OS provisioning using
Application Deployment Automation, if the SA OS
Sequence in use includes a device group and
multiple servers are provisioned simultaneously,
some of those server provisioning jobs will fail with
the following error:
Unexpected general exception: com.opsware.device.DeviceGroupVO.modifiedDate
is set to the illegal value.

 Linux, Solaris, Windows OS Provisioning Do not include any device groups in your OS Sequence.
QCCR1D118372

SA fails to complete OS provisioning if the net or subnet from which the machine obtains its IP address does not have PTR records associated with the IP address.

Red Hat Linux 4 and 5 Power OS Provisioning Make sure that there are PTR records associated with the IP address or
specified in /etc/hosts on the OS provisioning DHCP server.
QCCR1D123158

Provisioning an unmanaged server and bringing it into the Managed Server Pool in a DHCP-less environment (using the linux6 option and HPSA_linux_boot_cd) does not work correctly.

 Linux OS Provisioning None
QCCR1D132825 SA loads the stage2 image from the CD instead of the NFS.
Red Hat Linux 6 OS Provisioning Eject the CD after you perform OS Provisioning.
QCCR1D136144

Running a single OS Sequence job against two servers with the same MAC address in different networks causes an exception.

 Independent OS Provisioning - Backend

If you have servers with the same MAC address in different networks, you must provision them sequentially. For example,  complete the Run OS Sequence job on the first server before you power on the second server.
QCCR1D136423

Provisioning dupe-mac Linux servers sequentially into a managed server, then reprovsioned the servers simultaneously should result in a Run OS Sequence job error.

 Linux OS Provisioning None
QCCR1D136445

If you attempt to register another server with the same MAC address as a mini agent after a server is in the OS Provisioning lifecycle, the Run OS Sequence job on the first server fails.

Independent OS Provisioning

Follow these instructions:

  1. Shut down the second server.
  2. Reboot the first server.
  3. Re-register the first server as a mini-agent.
  4. Re-run the OS Sequence steps.
QCCR1D136592

After a server is registered with SA as miniagent, if you then attempt to register a second server with the same MAC address (but with a different service operating system than the first server) as a miniagent, the registration fails. Then, if you shut down the second server as instructed, the Run OS Sequence job against the first server fails with an error.

 Linux OS Provisioning

When this problem occurs, you must

1. Ensure the second server remains shut down
2. Reboot the first server and  re-register it with SA as miniagent
3. Run the Run OS Sequence job against the first server again

QCCR1D137408

WIM-based OS provisioning is not supported.

 Windows Server 2008 R2 Itanium OS Provisioning None

Patch Management for Solaris

QCCR1D100566

Although the reboot is performed correctly, when you preview remediating a patch policy on a server, or view the job status for a patch policy that is already remediated, the reboot setting might incorrectly display “Install and Reboot Later” when it should display “Install and Reboot”.

 Solaris Patch Management - Solaris A workaround is not required because the reboot is performed correctly,
even though the display may be incorrect.
QCCR1D111342

Importing clusters with old names using
the solpatch_import command will fail because
Oracle has renamed their Solaris patch clusters -
the clusters in your SALibrary may not match the
cluster names from Oracle on Sunsolve.

 SunOS 5.6 - 5.10 and SunOS 5.10 x86 Patch Management - Solaris Download the latest supplement file from HP LNc. For complete
instructions, see “Obtaining the Solaris Patch Supplementary
Data File” in the SA User Guide: Application Automation.
QCCR1D114156

The solpatch_import –filter option does
not display recommended and/or security
patches if they had previously been marked
obsolete. This became an issue on June 4,
2010 when Oracle changed the criteria for
recommended and security patches
(described here: http://blogs.sun.com/patch/
entry/merging_the_solaris_
recommended_and).

Solaris Patch Management - Solaris Users with an existing metadata database (solpatchdb) must
delete the solpatchdb.zip, solpatchdb-old.zip and
solpatchdb_supplement.zip files and run create_db
to have support for recommended obsolete patches.

You must recreate the Solaris patch metadata database
(solpatchdb) if the following are true:
  1. You use the solpatch_import –filter option.
  2. You have run solpatch_import –update_db on
    June 4, 2010 or later.


After you have installed SA 9.01, perform these tasks to recreate
the metadata database (solpatchdb):
  1. Log in to the SA Client.
  2. Select Library in the Navigation pane.
  3. Select By Folder.
  4. Navigate to /Opsware/Tools/Solaris Patching.
  5. Delete the following files:
    • solpatchdb.zip
    • solpatchdb-old.zip
    • solpatchdb_supplement.zip


Follow the steps to create a new metadata database (solpatchdb)
as described in the SA User Guide: Application Automation,
Patch Management for Solaris.
QCCR1D136048

When you import the most recent recommended Oracle clusters, the following type of error is displayed:

[root@orange3 bin]# echo 'Recommended OS Cluster Solaris 10 x86' | /opt/opsware/solpatch_import/bin/solpatch_import -v -a policy -l /jk_hpu/Recommend1086cluster__policy

result:
failed with following error:
Importing patch cluster Recommended OS Cluster Solaris 10 x86
######################################################################## 100.0%
Uploading to HP SA Library
<….>
Due to errors importing, not creating policy
Not all patches handled successfully. Examine the errors below and retry.
Recommended OS Cluster Solaris 10 x86: Unable to update README

SunOS Patching

Contact HP Support (www.hp.com/go/hpsoftwaresupport) to obtain the following:

  • Binary unzip file
    You must unzip and install this file in /usr/bin. 
  • Hotfix files:

    • action_blob.py

    • libsolpatch.pyc
QCCR1D138562

Remediation jobs fail with the following traceback:

"'error': {'traceback': 'Execution error: Traceback (innermost last):\n File "./base/wayfuncs.py",
line 136, in evaluator\n File "<string>", line 6127, in ?\n File "<string>",
line 6121, in main\n File "<string>", line 5827, in action\n File "<string>", line 5226, in actionImpl\n File "<string>",
line 4620, in getPkgUnits\n File "<string>", line 2031, in pkgUnitStart\n File "<string>",
line 2193, in setProgress\nOverflowError: long int too long to convert\n', 'key': 'ACTION'}}}"

 


 

 32-bit UNIX platforms that are running agent versions with Python 1.5.2, and running jobs with SA Command IDs greater than nine (9) digits Patch Management Backend Contact HP Support to request the corresponding hotfix and follow their instructions to apply the hotfix to your system.

For more information, visit the HP Support web site at: HP Software Support Online.

 

Patch Management for Windows

QCCR1D102713

If a patch policy contains one or
more superseded patches, the
number of total rules counted after
remediating or patch installation
is incorrect. Note that the
compliance state of the server is
accurate before and after remediating.

 Windows Patch Management - Windows - Backend None
QCCR1D105098

Automatically installing recommended
Microsoft patches Q934041 (2000) and
Q924883 (MS07-014) fails. Manually
installing the patches results in a
Non-Compliant server status and a
dialog that is displayed:

Update has already been applied or is
included in an update that has already
been applied.

 Windows Patch Management - Windows - Backend Since the patch is not required, set a “never install” exception on
the patches.
QCCR1D108451

Windows Patch 944036 (installer for
IE 8) reports install failure (and returns
a non-zero exit code) on Windows Server
2008 x64 managed servers, even though
the patch is installed correctly.
Subsequent patch and compliance
scans will indicate the patch is installed
and compliant.

 Windows Server 2008 x64 Patch Management - Windows - Backend A workaround is not required because the patch job succeeded,
even though an error displayed.
QCCR1D110257

If you try to install the March 2010
(or later) MBSA patch database, and
then attempt to install MS10-015
(KB977165) and MS10-021 (KB979683)
on to a Windows Server 2008 x86 using
a Windows Patch policy, the Patch install
job results will incorrectly indicate success.
After a patch compliance scan, SA will still
report the patches as recommended for
the server, and the server will be listed
as non-compliant.

 Windows Server 2008 x86 Patch Management - Windows - Backend
  1. To install these patches, import the April 2010 (or later)
    version of the BSA Essentials Network patch supplement
    from the BSA Essentials Network on to your SA core server.
  2. Visit http://support.microsoft.com/kb/980966/ to download
    KernelSystemStateCheck.exe to determine whether the
    patch can be installed on your Windows Server 2008 (x86)
    managed servers.
  3. Contact HP Server Automation Support in order to get this file
    “qc110257.pyc”. (The Quality Center bug report number is
    QCCR1D 110257.)
  4. On the SA core, copy qc110257.pyc to the SA core’s Data
    Access Engine (spin) server.
  5. As root on the SA Data Access Engine (spin) server, execute
    the following command:

    # /opt/opsware/bin/python2 qc110257.pyc

  6. Assuming Microsoft's KernelSystemStateCheck.exe utility reports a pass result, use the ad-hoc Install Patch task window to install the version of MS10-015 (KB977165) that has a file name of
    Windows6.0-KB977165-x86.msu, and the version of MS10-021
    (KB979683) that has a file name of Windows
    6.0-KB979683-x86.msu.
Note: The Install Patch job progress may show “Was Not Installed” or
“side effect” messages. These progress messages may not be accurate.
The true indicator of whether these patches installed or not is when after the
Install Patch job completes (with reboot), MS10-015 (KB977165) and
MS10-021 (KB979683) are no longer recommended, and the compliance
indicators for these patches no longer show a red X.

Note: The SA Client will show the mpsyschk.exe version of these patches as
recommended or installed.
QCCR1D110471

Attempts to install the patch for
KB944036 (Installer for IE8) using SA will fail.

 

Windows Server 2008 x86

 

 Patch Management - Windows - Backend Log on to the managed server and install the patch for KB944036 manually.
QCCR1D111397

After remediating the vendor recommended
policy on a Windows managed server,
the server's recommended patch list shows
additional patches that need to be installed,
requiring the vendor recommended policy
to be remediated again. This sometimes
occurs when older patches introduce
problems that newer patches already fixed.

 Windows Patch Management - Windows - Backend None

SA Client (Framework)

QCCR1D105671

 The SA Client cannot be installed under
a localized (I18N) directory if the directory
path contains non-ascii characters.		 Windows SA Client Framework Install the SA Client Launcher in a path containing only ascii characters.

SA Client (Search)

QCCR1D66448 Some discovery dates for SAN arrays,
NAS filers, and switches will not display
as expected, although they are
technically correct, if the user profile is
set to a non-UTC timezone for Storage
System Discovery Date.		 Independent SA Client (Search) None

SA Command Center

QCCR1D118067

Chinese Date format: Commonly used date
formats, like yyyy ’year’ mm ‘month’ dd ‘date’
and ‘yyyy-mm-dd’ are not listed in the user
profile setting, so users cannot select a
favorite date format.

 Win2008 Win2008 R2 SA Command Center - Web None
QCCR1D118068

User’s  preferred  datetime format is:
“星期五 十月 22, 2010 15:16 CST”, but in
the SA Web client, all dates and times are
displayed as “Fri Oct 22,2010 14:04 CST”

 Win2008 Win2008 R2 SA Command Center - Client Framework None
QCCR1D135460 Cannot select any servers by clicking the square button next to the server in any of the extensions under Run Custom Extensions.
 Windows SA Command Center - Web Enable your browser Compatibility View option.

SA-NA Integration

QCCR1D90653

SA 7.8x and SA 9.x with NA7.5x integration
fails.

 Independent SA/NA Integration

Perform the following actions:

  1. In the jboss_wrapper.conf file, comment out the
    following lines: #wrapper.java.additional.6=-Dorg.omg.
    CORBA.ORBClass=com.sun.corba.se.internal
    .Interceptors.PIORB

    #wrapper.java.additional.7=-
    Dorg.omg.CORBA.ORBSingletonClass=
    com.sun.corba.se.internal.corba.ORBSingleton

    #wrapper.java.additional.8=-
    Xbootclasspath/p:/opt/NA/server/ext/wrapper/lib/
    CORBA_1.4.2_13.jar

  2. Restart truecontrol.

SA-SAR Reports

QCCR1D105234

In the SA Client in an NA-enabeld core,
if you run the Connections by Network
Device report and set the parameter to
Device Name Equals [Any Value], the search
returns no results.

 Independent SA Client Reporting Run the report using the following parameters:

Device Contains
QCCR1D107293 Scheduled reports exported to .xls do
not display charts or graphs
(“Unsupported Image error” is displayed
instead). However, tables are sent correctly.
Graphs are not visible in the .xls file, but the
report should not display empty image blocks.		 Independent SA Client Reporting None
QCCR1D112434

The “Application Deployment” and “Patch”
folders and their reports in the BSA
Essentials/SAR Client 2.0/2.01 installation
patch are missing. These folder definitions
are required to view the Application
Deployment and Windows patch reports.

 Independent SA Client Reporting After you complete the installation process for BSA Essentials
2.0/2.01 patch and download content from the BSA Essentials
Network for the product/stream you subscribe to, complete
the following steps:

Log in to a BSA Essentials core server.

  1. Change your user to become the BSA Essentials
    super user on the server:
    su - ombd
  2. Enter the following commands:

    cd /opt/opsware/omdb/deploy/birt.war
    cp report_def.xml report_def_org.xml
    vi report_def.xml
  3. Add the following two lines in the section of the
    report_def.xml     file:

    application_deployment_reports

    top_level_patch_reports

    Example: <folder name="reports">

    <display_name>Reports</display_name>

    <folder_reports></folder_reports>

    <subfolders>

    <subfolder_name>
    application_deployment_reports< /
    subfolder_name>

    <subfolder_name>top_level_patch_reports
    </subfolder_name>

    .....

    .....

    /subfolders>

    <parent>none< /parent>

    < /folder>

  4. Save the report_def.xml file.
  5. Launch the BSA Essentials Java Client.
  6. Click on the Reports folder to see the
    “Application Deployment” folder and
    “Patch” folders.

SA Web Client

QCCR1D109000

Internet Explorer enhanced with Security
Configuration (IE ESC) that is enabled to
access the SA Web Client blocks some features
of SA Web, such as the search function.

 

 Independent SA Web Client

There are two solutions to this issue:
1. Add the SAS Web core URL to IE's trusted sites list.
When using IE with ESC enabled to access the
SA Web Client core login page, you will be asked
whether or not to trust the core web site. You must
click the Add button in order to add the core web site
to the list of trusted sites.
To Manually add the core URL to the trusted sites list,
in IE select Tools > Security > Trusted Sites.
Enter the entire URL (for example, https://192.168.181.130)
and then click Add. Restart your browser to ensure all new
settings are accepted.
2. Disable IE ESC altogether.
Go to the Server Manager (the first icon near the
Start Menu on most systems, or the top left hand side
icon on all configurations). The Server Manager view
should be automatically selected on the left side panel.
On the right side panel, there is a Group label named
Security Information. On the right hand side of the pane,
in Security Information, click the link named Configure
IE ESC. For both Administrator and Users, select Off
and then click OK. Restart your browser. IE ESC is
now disabled.

Satellites

QCCR1D91097

In some cases, in the SA Web Client Manage
Gateway page, changes to bandwidth throttling
values between two gateways do not persist.

 Independent Satellites

You must apply any bandwidth changes between
gateways on the Core
Gateways only. Changes made on other gateways
will not take effect.

QCCR1D97659

Network scans to a satellite realm fail for
hosts with the error:
XML document structures must start
and end within the same entity.

 Windows Satellites In the SA Client Options select Tools > Options
> Unmanaged Servers > Advanced and remove
the argument -S %GATEWAY_IP% from the NMAP
parameters. The network scan should complete
successfully.

Script Execution

QCCR1D79545

Exporting a Run Server Script Job output
containing multi-byte characters
(Japanese/Korean) to .csv results in question
marks in place of the multi-byte characters.

 Windows Script Execution Export the job results in .txt format to eliminate the
garbled text.

SE Connector

QCCR1D88755

There is no Target and Target Volume
information displayed in the storage volume
access path view for a LUN

 Independent SE Connector None
QCCR1D91582

When you perform a provisioning operation
for an HP EVA array (such as create, delete,
or modify a volume or pool), the changes for
the volume or pool might not be immediately
available in the corresponding Inventory view
in SA after running the "Update from Storage
Essentials" process.

 Independent SE Connector After 30 minutes has lapsed, run the "Update from
Storage Essentials" process again. See the Storage
Essentials SRM Software User Guide for information
about provisioning EVA arrays.
QCCR1D105778

When a server on which SE Connector is
running is directly deactivated and deleted,
selecting Administration > Storage Scanners >
<The names of the SE Scanner on "Host">
shows stale entries of Storage scanners in the
Scanner panel. The stale entries count will
increase, depending on how many times the
server is deactivated and deleted from the core.

Independent SE Connector Manually delete the inactive Storage Scanner entries
from the Storage Scanner panel by using the Remove
menu option provided for each entry.

Server Automation Installer

QCCR1D111215

Restoring OS Provisioning Stage 2 images
fails on SUSE Enterprise Linux 9, which is a
deprecated platform.

 SUSE Enterprise Linux 9 Installer You can restore the OS Provisioning Stage 2 images by
manually running the restore_stage2.pyc script. This
script is located in:
<distro>/opsware_installer/tools/
restore_stage2.pyc

Software Management

QCCR1D100754

You cannot set the timeout value for the time
it takes to install or remove software or execute
scripts to anything other than the default value
of 5 hours - the job times out at 5 hours.
This timeout value is specified by
"way.remediate.action_timeout" in the
SA Web Client.

The job fails with the message "The request
to retrieve information from the Agent failed
because it timed out. If the problem persists,
please contact your HP Server Automation
Administrator."

 Independent Software Management None
QCCR1D101517

After performing a software remediation, the
compliance status might incorrectly show servers
as being out of compliance, because there is a
caching delay in the Web Services Data Access
Engine (twist).

 Independent Software Management Run a Software Policy Compliance scan. This will show
the correct compliance status. For more information,
see "Software Compliance" and "The Software Policy
Compliance Scan" in the SA User Guide: Application
Automation.
QCCR1D102564

Software Compliance scan status displays a Scan
Failed status after attaching and remediating a
software policy if the file solpatchdb.zip (the solaris
metadata database) is missing.

 Solaris Software Management - API Compliance Use solpatch_import to create the metadata database.
See the Patch Management for Solaris in the
SA User Guide: Application Automation for more
information about solpatch_import.
QCCR1D102934

If you run a large remediate job (for example,
500 servers), you might encounter a Web
Services Data Access Engine (twist) cache
full exception while running compliance
across the servers.

 Independent Software Management - API Compliance Increase the cache size.
QCCR1D111356

When using WebService API to invoke
SoftwarePolicyService.create(), if you set the
RPM package in the installable item list by using setInstallableItemData(), the install list is
not created.

 Independent Software Management - API Software Policy Use UAPI or webServiceAPI by calling
setSoftwarePolicyItems().
QCCR1D115665

Migrating a Windows Server 2008 R2 x64 server,
attached to a dynamic device group with the rule
Operating System=Windows Server 2008 x64
specified, prevents all Application Configurations,
remediated using a Software Policy, from being
detached from the server.

 Windows Server 2008 R2 x64 Software Management None
QCCR1D137070

After installing the OCLI package and running the oupload/odownload commands, the following error is displayed:

RuntimeError: Bad magic number in .pyc file

RHEL 5 Server X86_64;
RHEL 5 Client X86_64;
OEL 5 X86_64; CENTOS 5 X86_64

 Software Management

If you encounter this problem, include the file login.csh or login.sh in your environment, depending upon which shell you use.

  1. For the shells csh, tcsh, and similar variants, re-enter the following command:
            source <installation_directory>/ocli/login.csh.
  2. For the shells sh, bash, ksh, and similar variants, re-enter the following command at the command line:
            source <installation_directory>/ocli/login.sh.

Storage Host Agent Extension

QCCR1D93630

LUNs that are multipathed by EMC PowerPath
are shown as both "ROOT" and "LUN" in the
Inventory > Storage > Volumes Panel
alongside LUNs that are correctly displayed.
The SCSI Bus number provided by PowerPath
(using the powermt command) does not match
the bus number of the disks (LUNs).

 Windows Storage Host Agent Extension None
QCCR1D93690

The Server > Relationships > SAN Switches
panel on a virtual server is empty/only displays
SAN switches to which the given server is
directly connected.
In some cases, a server may depend on SAN
switches that are not displayed in this panel.
For example, a virtual server may be using
storage allocated from a hypervisor that was
allocated storage from a SAN.

 Independent Database Scanner for Oracle None
QCCR1D105382

When you run the storage snapshot specification,
the disk capacity information is changed in the
Inventory > Storage > Disk panel. This occurs
if there is a mismatch in the disk names, as
reported by the hardware registration script
and the storage snapshot specification.

 Windows 2008 Storage Host Agent Extension Reboot the server after changing disk information
(such as installing or uninstalling multipathing software,
presenting new LUNs, deleting LUNs, and so on),
and run the hardware registration before running
the storage snapshot specification.
QCCR1D105953

An EMC Symmetrix array that is discovered
through SE Connector can report more than
one storage volume with the same LUN number
presented to a managed server. Running the
storage snapshot specification on the managed
server will succeed; however, the Inventory
> Storage > File Systems and Inventory
> Storage > Managed Software panels
will be empty. In addition, some host volumes
with a LUN service type will not be displayed
in the Storage > Inventory > Volumes panel.

 Independent Storage Host Agent Extension None
QCCR1D106400

The right-hand panel under
Inventory > Storage > Volumes does not
display the supply chain and composition
information properly (or the information is
missing altogether) for some volumes that
were created out of LUNs

 AIX Storage Host Agent Extension Delete the stale volumes on the AIX managed server and
run the storage inventory snapshot specification.
QCCR1D106699

For managed servers with mirrored volumes,
if one of the disks that is part of a mirrored
volume fails or is removed, the state of the
volume is shown as "Failed Redundancy"
in the Disks Management panel. However,
in the Inventory > Storage > Volumes panel
for the managed server, the status of this
volume is shown as "OK", even after running
storage snapshot specifications.

 Windows 2008 Storage Host Agent Extension None
QCCR1D107944

Running a storage snapshot specification on
unsupported ESX 3.0.x servers returns an error
message that indicates unsupported namespace
in content of SOAP body. Storage related
information for ESX 3.0.x is not stored and displayed
in the SA Client.

VMware ESX 3.0.x Storage Host Agent Extension None
QCCR1D111724
/111727

Host Storage Inventory does not support VMware
servers that have VMDK on NFS datastore. Therefore,
no storage information will be collected on VMWare
servers with this configuration.

 All VMware servers Storage Host Agent Extension None
Bug ID: 149406 / QCCR1D60760

Solaris LVM RAID on Soft Partition on slices stops
responding, resulting in a defective storage supply
chain.

 Independent Storage Host Agent Extension None
Bug ID: 149707 / QCCR1D61061

The SNIA v1 HBAAPI Extension reports two single
port cards when a single dual port card is present
in a multi-port card.

 Independent Storage Host Agent Extension None
Bug ID: 151921 / QCCR1D63275

When you add a mirror to concatenated or stripe,
there is no distinction between the volume types
"Mirror Concatenated" and "Mirror Striped" in the
Volume Manager labels. Note that
"Mirrored Concatenated" and "Mirror Striped" are
distinct on the volume manager on the host, such
as on the Veritas Volume Manager.

 Independent Storage Host Agent Extension

None

The type of volume manager might not match the
native tool, such as the Veritas Volume Manager.
The STORAGE_TYPE value is the immediate node
in the supply graph, which is the storage type of the
most decendent volume.

Bug ID: 152016 / QCCR1D63370

The value stored in
STORAGE_COMPONENTS.STORAGE_DRIVE is a
different format on Solaris 5.10 than on Solaris 5.8
and 5.9. The different format for 5.10 causes a
broken storage supply chain on affected servers.

 Unix Storage Host Agent Extension Check the version number in the /etc/format.dat file on
the server. If it is less than 1.28, update the file.
Bug ID: 152942 / QCCR1D64296

On a Windows 2003 server with the SNIA library
from QLogic 9.1.4.15 HBAAPI, Fibre Channel
Adapter and storage volume information might
not be discovered by the Storage Host Agent
Extension, causing fibreproxy.exe to stop
responding.

Windows Storage Host Agent Extension For Windows Server 2003 and Microsoft Windows 2000
operating systems, use the native Microsoft SNIA library
instead of the SNIA that is provided by the QLogic driver.
Download the Fibre Channel Information Tool to add the
Microsoft HBAAPI support to the operating system.
For Windows 2003 SP1 or later, the Microsoft HBAAPI
support is built in. If the SNIA's version of hbaapi.dll is
installed on the operating system, remove it.
Bug ID: 154418 / QCCR1D65772

When you snapshot a Unix server that has a
QLogic driver installed, there is no:
FC adapter information in the Hardware view.
Composition and connectivity information for any
SAN volume in the Volumes pane.

 Independent Storage Host Agent Extension Install patches 108434 and 108435 on Solaris 8 SPARC
servers. The Storage Host Agent Extension on Solaris
5.8 SPARC requires these patches.
Note: There is no known workaround for Red Hat 3 or
Red Hat 4 servers using QLogic controllers.
Bug ID: 154971 / QCCR1D66325

Veritas Storage Foundation 4.3 with QLogic
9.1.4.15 results in invalid fibre proxy SCSI
addresses. The SAN storage volume displays
both LUN and Root as the Service Type. There
are two lines for the physical drives: One line
displays LUN and the other displays Root.

 Independent Storage Host Agent Extension None
Bug ID: 155476 / QCCR1D66830 The file system is not displayed on the server
storage file system panel when the partition and
format on the Windows server is mounted to an
empty NTFS folder. There is no support for mounting
Windows 32 file systems on non-drive letter locations.		 Windows Storage Host Agent Extension

None

Note: The Storage Host Agent Extension does not report file
systems that have non-drive letter mount points.
The Storage Host Agent Extension does not report file systems
that have multiple mount points.

Bug ID: 157044 / QCCR1D68398

Fibreproxy is broken on Windows 2000 SP4 server
with a QLA2310 HBA and vendor driver version
9.1.4.10. A storage inventory snapshot does not
gather and supply complete data, including storage
volume and FCA information.

Windows Storage Host Agent Extension None
Bug ID: 157579 / QCCR1D68933

When you run take a Storage Host Agent Extension
snapshot by running fibreproxy on a Windows server
where Emulex LP850, LP952, LP9002, or LP9402 is
installed, three FibreChannelTargetMappings are
returned, two of which are duplicates. This symptom
does not occur with Emulex driver 1.30a9.

 Windows Storage Host Agent Extension None
Bug ID: 158923 / QCCR1D70277

If you run the chpath command as shown below to
take a Storage Host Agent Extension snapshot for
each available path to the device, all the MPIO paths
to a logical device become disabled. In this state,
the system calls used by the diskproxy and mpioproxy
will stop responding.
chpath -l hdisk2 -p fscsi0 -s disable xx

 AIX Storage Host Agent Extension None
Bug ID: 159156 / QCCR1D70510

After you update a LUN mapping (and remove the
initiator ports) from a mounted SAN volume on a
server, the old LUN mapping information still
displays in the SAN array volume view and in the
server storage volume view. An additional access
path is displayed in the SAN array volume view
(Access Path subview) for the volume for which
LUN mapping was removed. The access path
that shows no initiator device and/or initiator port
information is the correct one. The incorrect access
path is removed from the display when the next
Storage Host Agent Extension snapshot is run.

 independent Storage Host Agent Extension Take a snapshot of the server to which the volume was
mapped or partitioned.
Bug ID: 159580 / QCCR1D70934

The SAV displays incorrect information after adding
a zone to a fabric. The zone is not associated to the
correct server/port/WWN.

 independent Storage Host Agent Extension None
Bug ID: 164951 / QCCR1D76305

The multipath information is not reported correctly
for a server that has HP-UX 11iv2 OS installed and
Veritas DMP managing the multipathing in the
SA Client. The SNIA library does not support HBA_GetFcpTargetMappingsV2r.

HP-UX 11iv2 Storage Host Agent Extension None
Bug ID: 168716 / QCCR1D80070

On servers running AIX 5.2 with PCI-X Fibre
Channel Adapters, the supply chain does not
display after taking an inventory snapshot.

Independent Storage Host Agent Extension None
Bug ID:168889 / QCCR1D80243

If you disable a volume in Veritas DMP and
subsequently take a new Storage Host Agent
Extension snapshot, it appears as if the the
updated volume is still managed by Veritas DMP.

 Independent Storage Host Agent Extension When constructing LVM modules on the HP-UX 11.31 platform,
use agile DSF devices. There is no workaround for other platforms.
Bug ID: 167103 / QCCR1D78457 If you perform a core upgrade to SA 7.50 and
ASAS 7.50 and then run the customer extension
to upgrade a Storage Host Agent Extension on
the host, the host disappears from the INTERFACE
table and the host's STORAGE_DRIVE does not
appear in the STORAGE_COMPONENT table.		 Independent Storage Host Agent Extension It may take one to two hours for the host and drives to repopulate
their tables. Verify that the host is present in the INTERFACE
table and that the STORAGE_DRIVE element is present in the
STORAGE_COMPONENT table.

Virtualization

QCCR1D90019 If a system has more than one virtual network
with the same name, even if those networks
are managed by different hypervisors,
scanning for virtual servers fails due to
a violation of unique name constraints.		 Windows Server 2008/Hyper-V Vritualization Do not use duplicate virtual network names.
QCCR1D106085 If your Hyper-V server has more than one IP
address, SA might change the Management
IP address from the one you registered to one
of the other IP addresses.		 Windows Server 2008 pre-R2 server Vritualization - Hyper-V To prevent this problem, you need to manage your
Windows 2008 pre-R2 server from a Windows 2008
R2 server and make sure the option to allow the
management operating system to share the network
adapter is not selected. The following gives the basic
steps to accomplish this, however, see your Microsoft
Hyper-V documentation for complete details. More
information may also be available by searching the internet
for "New in Hyper-V Windows Server 2008 R2" and
"Hyper-V Remote Management: You do not have the required
privileges to complete this task."
Make sure the administrators on the pre-R2 and R2 servers
have the same password.
Log on to the R2 server and start the Hyper-V Manager applet.
Right-click on the Hyper-V Manager and select Connect to Server.
In the Select Computer window, select the "Another Computer"
radio button and enter the name of the pre-R2 server.
An icon for the pre-R2 server will appear in Hyper-V Manager.
Select the icon for the pre-R2 server and open the Virtual
Network Manager.
Highlight the NIC whose configuration you need to change.
Under the Connection type, unselect "Allow management
operating system to share this network adapter."
Click OK.
QCCR1D104418 The reported OS property text for ESX servers
is inconsistent between direct (SA Agent) and
indirect managed (vCenter) cases.		 VMware ESX (all versions) Vritualization - Backend (VMware) None
QCCR1D105999 After cloning an SA-managed virtual machine, when
the clone starts up for the first time but cannot obtain
network connectivity, agent revival will fail to create a
new server record for the cloned MVM.		 Independent Virtualization - Backend (VMWare) Restart the agent on the cloned machine after network
issues are resolved and the agent will correctly register
as a cloned MVM.
QCCR1D106909 Clone Virtual Machine job will fail the Registering
Server step if the Windows Shutdown Event Tracker
is enabled on the source virtual machine. This is
because the Shutdown Event Tracker waits for user
input before it completes rebooting, so the SA Agent
registration cannot complete.		 Windows Vritualization Disable the Shutdown Event Tracker on the clone
source virtual server. Windows 2003 x64 cloning
requires a manual reset to resume virtual machine
images customization.
QCCR1D109887 The snapshot view is not available on an ESX server
that is managed by vCenter.		 Red Hat Linux Vritualization Manage ESX directly snapshot view.
QCCR1D110035 When a hypervisor that is dual-managed (through
Virtualization Service and SA Agent) loses one of its
management paths (such as when. the Virtualization
Manager or VCenter is removed from SA), the Login
Credentials panel does not display in the server
browser panel and the hypervisor credentials do not
display in the Properties view.		 VMWare ESXi Vritualization Right-click on the hypervisor, select "Refresh Server",
and then press F5 (Refresh) to refresh the client so that
the Login Credentials panel displays in the server browser.
QCCR1D111307 If you add an ESXi server with larger hardware
configuration data, the add operation suspends
processing.		 ESXi Virtualization - Backend (VMWare) Reconfigure the server with fewer CPU counts in hardware
information.
QCCR1D111780 Hypervisors are not loading. Windows Virtual Center Check that the hypervisor version you are using is supported.
Or check to see if the hypervisor is in a NOT RESPONDING state.
QCCR1D111789 Adding two vCenters concurrently results in
one of the automatically triggered reload data
to suspend processing.		 Independent Virtualization - Backend (VMWare) Add the vCenters separately.
QCCR1D111922 The Create Virtual Machine operation on an
SA managed ESX 3.5 server fails with an
error message of com.vmware.vim25.
VirtualMachineConfigSpec. 		ESX 3.5 Virtualization - Backend (VMWare)

After the SA 7.5 release, one of the VMM library jar files
was changed from OPSWvmm-vmware.jar to
vmm-vmware.jar. When an upgrade is performed from
SA 7.5 directly to SA 9.0, or from SA 7.5 to SA 7.8 to SA 9.0,
and any virtualization operation is invoked on the ESX
hypervisors, the VMM package gets remediated first with
the new package but the OPSWvmm-vmware.jar file is
left untouched. This causes the consecutive virtual
machine create operations to fail.
The following workaround is intended for any ESX hypervisor
that is managed by an Agent in SA and whose virtualization
aspect will still be handled through the same route (not via VS)
in SA 9.0.

    1. Create a script.
      1. From the Navigation pane, select Library > By Type > Scripts >
        Unix.
      2. From the Actions menu, select New and then enter the following
        information:
        Name: Clean VMM on ESX
        Location: Select Package Repository > All VMWare Linux >
        VMWARE ESX Server <any version>
        Script Content:
        1. unlink /opt/opsware/vmm/lib/OPSWvmm-vmware.jar >
        /dev/null 2>&1
      3. Description: Enter a brief description, as necessary.
      4. Leave the defaults for the remaining fields and then select
        File > Save to save and close the window.<
    2. Create a dynamic device group and add the target servers
      to this device group.
    3. Run the script on the servers in the device group created above.

    Note: This script can be used on all ESX versions.
    There is no need to duplicate it in different packages
    or to create a separate device group for each hypervisor version.

QCCR1D111972 Create Virtual Machine fails on a directly
managed ESX hypervisor if the virtual
machine's datastore name contains
special characters. 		ESX Virtualization - Backend (VMWare) Change the datastore name so that it does not contain
special characters.

Web Services Data Access Engine
QCCR1D111039 An out-of-memory error is encountered in
the Web Services Data Access Engine		 Red Hat Linux/Solaris Web Services Data Access Engine (twist) The default maximum heap size for Web Services
Data Access Engine has been increased to
2560MB from 1280MB.
QCCR1D112222

The Web Services Data Access Engine
does not start and records the error:

Could not reserve enough space for object
heap in:
/var/log/opsware/twist/boot.log

The default maximum JVM heap size has
been increased to 2560 MB, and as a result,
the Web Services Data Access Engine (twist)
does not start properly on Linux AS3 32-bit
systems due to a two-gigabyte memory limit
for a single process running on JVM on 32-bit
systems.

 Platform: Red Hat Enterprise
Linux AS3
32-bit		 Web Services Data Access Engine (twist)

Before upgrading, edit the file:

/etc/opt/opsware/twist/twistOverrides.conf
and add the following entry:
twist.mxMem=<memory size in Megabytes>
The value must be 2000 megabytes or less.
Example: twist.mxMem=1960m

QCCR1D134675

The PyTwist library contains some inconsistent attribute names with the attribute names of the objects returned from an API call.

The following attributes list contains the inconsistent attributes:

- class: "com.opsware.apx.APXVersionRef", attributes: "aPXType"
- class: "com.opsware.apx.APXVersionVO", attributes: "aPX"
- class: "com.opsware.apx.NoCurrentVersionException", attributes: "aPX"
- class: "com.opsware.apx.ProgramAPXJobInfoVO", attributes: "aPX"
- class: "com.opsware.apx.ProgramAPXVersionRef", attributes: "aPXType"
- class: "com.opsware.apx.UnApprovedVersionException", attributes: "aPX"
- class: "com.opsware.apx.UniqueVersionLabelException", attributes: "aPX"
- class: "com.opsware.apx.WebAPXVersionRef", attributes: "aPXType"
- class: "com.opsware.busapp.BusinessAppContact", attributes: "vCardData"
- class: "com.opsware.compliance.sco.policy.AppConfigRule", attributes: "cML"
- class: "com.opsware.compliance.sco.policy.FileCMLMapping", attributes: "cML"
- class: "com.opsware.compliance.sco.policy.SMORule", attributes: "cFL"
- class: "com.opsware.compliance.sco.AuditPolicy", attributes: "sCOPolicy"
- class: "com.opsware.fido.apx.APXAuthorizationDeniedException", attributes: "aPXId"
- class: "com.opsware.fido.apx.APXPermissionExistException", attributes: "aPXId", "aPXVersionId"
- class: "com.opsware.fido.apx.APXPermissionNotFoundException", attributes: "aPXId", "aPXVersionId"
- class: "com.opsware.fido.apx.APXSecurityException", attributes: "aPXContext"
- class: "com.opsware.fido.MissingPermissionsException", attributes: "sQL"
- class: "com.opsware.fido.TablePermissionsMissingException", attributes: "sQL"
- class: "com.opsware.nas.IPAddressInfo", attributes: "iPType"
- class: "com.opsware.nas.NetworkACLVO", attributes: "aCLId", "aCLType"
- class: "com.opsware.nas.NetworkDeviceVO", attributes: "nATIPAddress", "nATRealmName", "rOMVersion", "tFTPServerIPAddress"
- class: "com.opsware.osprov.AutomaticProvisioningRule", attributes: "oSSequence"
- class: "com.opsware.osprov.OSBuildPlanJobInfoVO", attributes: "oSBuildPlanRef"
- class: "com.opsware.osprov.OSSequenceJobInfoVO", attributes: "oSSequenceJobParams"
- class: "com.opsware.osprov.OSSequenceJobParams", attributes: "oSSequence"
- class: "com.opsware.pkg.aix.BaseFilesetVO", attributes: "lPP"
- class: "com.opsware.pkg.aix.UpdateFilesetVO", attributes: "lPP"
- class: "com.opsware.pkg.RelocatableZIPVO", attributes: "zIP"
- class: "com.opsware.script.OGFSScriptJobArgs", attributes: "xArgs"
- class: "com.opsware.shared.TwistConsoleService", attributes: "aPIVersion", "aPIVersionLabel"
- class: "com.opsware.storage.DeviceInitiatorView", attributes: "mPIO", "mPIOVersion"
- class: "com.opsware.storage.LogicalVolumeTargetView", attributes: "mPIO", "mPIOVersion"
- class: "com.opsware.storage.StorageInitiatorSummary", attributes: "sANVolumeCapacity"
- class: "com.opsware.swmgmt.ismcontrol.ISMData", attributes: "iSMAppName"
- class: "com.opsware.swmgmt.ismcontrol.RunISMControlJobArgument", attributes: "iSMControl"
- class: "com.opsware.system.recert.CoreRecertPhaseArgument", attributes: "cADBPassword"
- class: "com.opsware.system.integration.FlowInputDetails", attributes: "aList"
- class: "com.opsware.virtualization.microsoft.HyperVConfigDetailsVO", attributes: "bIOSBootOrder", "vMLocation"
- class: "com.opsware.virtualization.microsoft.HyperVHypervisorVO", attributes: "vMDefaultConfigLocation", "vMDefaultDiskLocation"
- class: "com.opsware.virtualization.microsoft.HyperVVMJobInfoVO", attributes: "vMConfigDetailsVO"
- class: "com.opsware.virtualization.vmware.VMJobElementProgress", attributes: "vMJobData"
- class: "com.opsware.virtualization.vmware.VMJobElementResult", attributes: "vMJobData"
- class: "com.opsware.virtualization.vmware.VMJobInfoVO", attributes: "vMConfigDetailsVO", "vMCloneSpec"
- class: "com.opsware.virtualization.vmware.VMJobProgress", attributes: "vMJobData"
- class: "com.opsware.virtualization.vmware.VMCloneSpec", attributes: "vMTemplate"

If one of these object types is created on the client side, the attribute name will be displayed as shown in the inconsistent attribute list.
If one of the object types is returned from an API call, the attribute present in the inconsistent attribute list will have a slightly different name (same letters, but the first letter will be capitalized, for example: "APXType", "APX", "VCardData", "CML").

For example:
This inconsistent attribute issue affects the PyTwist's AuditPolicy class. When an AuditPolicy object is created on the client side using the PyTwist library, the object attribute name is "sCOPolicy", but when an AuditPolicy object is returned by an API call, the attribute name is "SCOPolicy" . This causes an AttributeError (on the object returned from the server) if the "getSCOPolicy()" method or the "sCOPolicy" attribute is invoked.

Independent Web Services Data Access Engine (twist) Avoid the AttributeError on the objects returned from the server by directly invoking the capitalized attribute names. This must be done only for the inconsistent attribute names mentioned in this description. For example: to receive the  value for the "sCOPolicy" attribute of the AuditPolicy, the "SCOPolicy" attribute name must be invoked directly on the objects returned from an API call.


Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Fixed Issues For This Release

This section describes customer-found fixed issues for this release. The table lists issues first by subsystem, then numerically within each subsystem.

QCCR1D Symptom/Description Platform

Agent

QCCR1D115666 Large number of SLES servers running SLES10 on the ext3 filesystem is not supported. Linux
QCCR1D130405 Incorrect text in asyncssl.py win 32 error handler error:
"errno.sock_err"		 Independent
QCCR1D130797

The number of guest CPUs are not reported correctly. Instead, the system erroneously reports the number of host CPUs.

Linux
QCCR1D131931 Agent Upgrade CX of agents fails to start because the Python executable cannot be found. Windows
QCCR1D132944 Linux bonding interfaces are not shown in inventory data for SLES 11 x64. Linux
QCCR1D133618 Agent deployment fails because the registration timeout is exceeded. HP-UX 11.31
QCCR1D135192 Dormant Agents fail to register if they have been dormant for 12 hours or more. Independent
QCCR1D135716 OGFS file access fails for non-administrator users. Windows

Application Deployment Manager

QCCR1D133282 Code component Base Directories allowed repeating file separators (multiple forward or backward slashes). Independent
QCCR1D133420 The admtool utility terminated when HP Database and Middleware Automation was not configured. Independent
QCCR1D133515 An error occurred when creating the ZIP file for a Code component if any file names contained multibyte characters. Independent
QCCR1D133572

In the Manage Application dialog, the "View Deployment Jobs" button was not enabled when deployment jobs were, in fact, associated with the selected version, and those jobs had not been undeployed or rolled back.

Note: All deployment jobs associated with a particular version must be undeployed or rolled back before that version can be deleted.

Independent
QCCR1D134763 Application Deployment Manager did not notify users of unsaved changes when leaving the Administration Settings page. Independent
QCCR1D134808

The admtool utility was extended to support partial import/export in Application Deployment Manager. (Enhancement)

 Independent
QCCR1D135050 The Application editor reported an "Expression Is Missing" validation error for the Default Install Path whenever a Code component was added or edited if the Sandboxing setting on the Administration tab was not set . Independent
QCCR1D136030 Destination directories for Configuration File components are now automatically created if they do not exist. (Enhancement) Independent

Audit and Compliance

QCCR1D119832 Running order ignored for audit policy with custom scripts that were added as rules.
 Independent
QCCR1D132380 The compliancy check is too wide for the screen. This results in a un-readable window. The user cannot determine the actual and policy values.
 Independent

Device Groups UI

QCCR1D134690 Custom Field filter with Equals Operator does not work correctly. Independent
QCCR1D134718 Filter rules of dynamic device groups are not displayed in a consistent order. Independent
QCCR1D135044 The graphical user interphase does not show event-based changes in dynamic-device groups, but the SA Command Center does. Independent

DSE UI (Scripts)
QCCR1D134084 Unable to pull job history for recurring extensible discovery jobs that had servers deleted prior to running the job. Independent

Gateway
QCCR1D90563 Core gateway fails with no errors when it can't open port 8085 for listening Independent

Global Filesystem - Backend

QCCR1D133602 When a job fails, the getResult global shell command does not work. Linux;Solaris

Model Repository
QCCR1D129684 Some older sessions are not deleted during garbage collection. Independent

OS Provisioning

QCCR1D129544

Provisioning SUSE Linux Enterprise Server in a non-DHCP environment is not supported in SA 9.x.

 Linux
QCCR1D133706 Import fails. Red Hat Linux Server

Patch Management

QCCR1D133203 Setting the hpuxpatch_dont_supersede custom attribute at the device group level should allow you to install superseded patches on a server contained in that device group. HP-UX
QCCR1D133701 The solpatch_import command only supports .zip formats - should support other format, such as .tgz, .tar.gz, and .tar.Z. Solaris

SA Command Center
QCCR1D133496 Cannot export audits to a comma-separated values (CSV) file. Windows
QCCR1D135496

When you submit a job through ADM, ADM reports that the job is complete at a much later time than SA Client does.

 Independent

Server Module (SMO)
QCCR1D132608 Improve the error message that appears when an incorrect server i18n encoding setting causes the Users/Group server module to fail. Linux

Software Management
QCCR1D112410 Sorting of remediation results causes undesired sorting behavior. Independent
QCCR1D115563 The following warning message is displayed when remediating a device group using a pytwist script in job logs, even though no server is removed from the remediation process and the process is successful:

If you start a device group remediation using a pytwist script, navigate to job logs, and then open the specified job, the following warning message is displayed:

"The action can't be performed on one or more of the selected items. The action will continue only for the applicable selected items."		 Independent
QCCR1D121549 If a policy is set to only run on a certain platform, the script object(s) attached to that policy should also only run on that platform. For example, in the setup defined in 'actual behavior', the script should only run once, not three times. UNIX
QCCR1D129781 During a software package update, the Java client uses excessive amounts of local CPU and memory resources, often resulting in PC shutdown.  Independent
QCCR1D132413 SA implementation of the rhn_import utility uses a deprecated field (package__md5sum), instead of the SHA256 digest, to retrieve a checksum, resulting in the following type of error:
Verifying package...Maximum retries exceeded: RHNDownloadVerificationError: Digest mismatch		 Linux
QCCR1D134769 Excessive load incurred on the Web Services Data Engine searching for custom attributes for large remediations. Linux;Solaris
QCCR1D137153

If you install a Solaris package that contains the characters "-R" in its name, SA erroneously reports that the installation has failed.

 Solaris

Software Repository
QCCR1D133980 Kernel-*-base Red Hat Package Managers (RPMS) are uploaded in "Update only" mode. SUSE Linux

Web Services Data Access Engine
QCCR1D133585 Multiple changes are not displayed:
* When running the ServerService.update() method. For example, log files should reflect field changes but the the changes are not displayed.
* When running multiple ServerVO changes. For example, ServerService.getLogEntries() should display the first or last action of the simultaneous update, depending on sort order.		 Independent
QCCR1D134996 The following exception occurs when saving a pre-installation script of a zip package:
com.opsware.common.IllegalValueException: com.opsware.pkg.RPMVO.installInfo is set to the illegal value com.opsware.pkg.InstallInfo@1851003
 Independent

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Deprecated Features

When a feature or platform is identified as deprecated for a release, it means that you (the SA customer) are notified of its future removal. Deprecated features are still fully supported in the release they are deprecated in, unless specified otherwise. The intent is that deprecated features or platforms will have support removed in the next major or minor SA release; however, eventual removal is at the discretion of HP.

The following features were deprecated in the SA 7.80 release. Current and future availability of these features is also described in the following sections:

Deprecated API Methods

In SA 9.0, moving application configurations and configuration templates into folders changed the behavior of the associated classes and services.

Attributes folder and lifecycle of the VO-s are required for the following API calls:

com.opsware.acm.ConfigurationService#create
com.opsware.acm.ConfigurationService#update
com.opsware.acm.CMLService#create
com.opsware.acm.CMLService#update

The following methods have been deprecated, but they still perform as expected. Method
com.opsware.folder.FolderVO#getCustomers should be used instead.

com.opsware.acm.ConfigurationVO#getCustomers
com.opsware.acm.CMLVO#getCustomers

The following methods have been deprecated and they have a void implementation. Method
com.opsware.folder.FolderVO#setCustomers must be used instead.

com.opsware.acm.ConfigurationVO#setCustomers
com.opsware.acm.CMLVO#setCustomers

Code Deployment and Rollback (CDR) and Configuration Tracking

Code Deployment and Rollback (CDR) was deprecated in the SA 7.80 release, but is still supported in SA 9.0. In a future release, this feature will not be supported. The new Application Deployment tool in SA 9.0 is intended to replace CDR. See New Application Deployment Manager on page 13 and the SA Application Deployment User Guide for more information.

For more information about the deprecation of CDR, contact your HP Technical Support representative.

Agent Deprecation

In SA 9.0, HP announced the deprecation of the Server Automation Agent for the following versions:

• Server Automation 7.01
• Server Automation 7.00
• Server Automation 6.xx
• Server Automation 5.xx

Although releases of HP Server Automation prior to 9.0 will continue to support these versions of the Agent, it is recommended that customers migrate to newer versions of the Agent on their managed platforms.

HP SA will stop supporting these versions of the Agent in an upcoming major or minor release. Agents from Server Automation 4.xx and earlier are not supported in this release.

DOS-Based OS Provisioning

DOS-based OS Provisioning was deprecated in the SA 7.80 release and is not supported in SA 9.0 or later. For more information, contact your HP Technical Support representative.

start_opsware.sh and stop_opsware.sh scripts

As of SA 7.80, the following scripts are no longer supported:

start_opsware.sh
stop_opsware.sh

In SA 9.0 and later you must use the unified start script:

/etc/init.d/opsware-sas

If you have any applications or scripts that depend on this script, you must rewrite them to use the unified start script.

Virtual Server Management Actions

The Open Console action (for VMware virtual machines of ESX agent-managed hypervisor) was removed in the SA 9.0 release.

The Open Web Access action (for ESX agent-managed hypervisors) was removed in the SA 9.0 release.

As of SA 9.0, virtualization actions for agent-managed ESX 3.0 hypervisors are no longer supported, unless the ESX 3.0 hypervisor is managed by a Virtualization Service. It cannot be directly added to the Virtual Servers view (through Add Hypervisor); it needs to be vCenter managed.

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

New In Previous Releases

 

9.04

 

Agents (9.04)

Faster Agent Installation

The process of bringing servers under SA management is considerably faster in SA 9.04. When you install the SA 9.04 agent to bring your servers under SA management, SA now installs the agent in parallel on multiple servers simultaneously so the performance is significantly improved. The agent deployment dialog displays the set of servers on which the agent is being installed. For more information on installing the agent and bringing servers under SA management, see the SA User Guide: Server Automation.

 

Application Deployment Manager (9.04)

In SA 9.04, the Application Deployment Manager introduces the ability to import and export application definitions in XML format using the admtool command line utility (see “Appendix A: Importing and Exporting Data” in the Application Deployment User Guide). This allows for migration of application definitions between separate meshes often used, for example, in Development and Production environments.

The Application Deployment Manager now enables you to specify a Base Path for Code components. The Base Path serves as a prefix for the Default Install Path. Both settings are specified in the Application editor. The Full Install Path (the Base Path followed by the Default Install Path) indicates where the Code component files will be installed on the target server. A list of valid Base Directories is maintained by the Application Deployment administrator on the Application Settings page. The administrator can enable or disable the use of a Base Path for all Code components.

Additionally, Application Deployment Manager 9.04 supports enhanced logging for SA-OO integration, allowing easier auditing of in-bound and out-bound OO interactions.

 

Database Scanner for Oracle (Storage) (9.04)

In order to monitor an Oracle 11G database with the SA Oracle Database Scanner, the XML DB and DBMS_NETWORK_ACL_ADMIN package must exist in the database.  The SA Oracle DB Scanner needs access to these objects in order to grant privileges and access for itself. If the objects do not exist, then the "pamuserprivilege.sql" script cannot complete its tasks and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database.

Before executing the SA DB Scanner "pamuserprivilege.sql" script in the Oracle database, first perform the following steps to install the XML DB and DBMS_NETWORK_ACL_ADMIN package in the Oracle 11G database. The steps can be done manually, or by using SQL scripts provided by SA.

To use the SQL scripts provided by SA :

The scripts are installed along with the APX into /opt/opsware/dbscanner.oracle/lib directory and are accessible in OGFS and can be copied from the following OGFS folder: /opsw/apx/runtime/script/com.opsware.server.module.storage.dbscanner.oracle.

To perform the steps manually:

  1. cd $ORACLE_HOME/rdbms/admin
  2. sqlplus /nolog
  3. SQL> connect <sys_user>/<password> as sysdba
  4. SQL> spool install_xml.log
  5. SQL> @catqm xdb sysaux temp NO
  6. SQL> @dbmsnacl.sql
  7. SQL> spool off;

 

Adobe Flash Player and the New SA Client Launcher – All SA Users (9.04)

SA 9.04 includes a new, required SA Client Launcher (version 1.5.0). Make sure that Adobe Flash Player is installed before you install the new SA Client Launcher. Every SA user (not just the SA administrator) must install both Adobe Flash Player and the new SA Client Launcher.

To ensure that you install these items in the right sequence:

  1. Download and install the latest Adobe Flash Player. You can download it from:

    http://fpdownload.adobe.com/get/flashplayer/current/install_flash_player.exe

  2. Download and install the latest SA Client Launcher included in SA 9.04. For complete instructions, see “Installing the SA Client Launcher” in the SA 9.0 User Guide: Server Automation.

Note: If the SA Client becomes unresponsive after you perform these steps, restart it.

 

HP-UX (9.04)

This release features support for HP-UX patching and HP-UX provisioning.

This releases also provides an Application extension for the management of Virtual Partitions (vPars) and Virtual Machines (HPVMs).

Download the document: HP-UX Virtualization for 9.04 from the 9.04 section of the Self-Solve Portal at: http://support.openview.hp.com/selfsolve/manuals.

 

Integration with NA 9.10 (9.04)

This release provides SA integration with NA 9.10.

Model Repository Host: Multiple Database Instances (9.04)

SA now supports multiple database instances on the database server where one of the instances is the SA Model Repository instance. The requirements, configuration and procedures for adding instances is the same as shown in the SA Simple/Advanced Installation Guide, Appendix A: Oracle Setup for the Model Repository.

SA-OO Integration (9.04)

Updates pertaining specifically to the OO-SA integration (Server Automation operations performed within Operations Orchestration) are delivered via the HP Live Network at https://www.www2.hp.com/.

 

Patching (9.04)

This release provides support for the following Solaris Fujitsu patching features:

 

Upgrades and Patches (9.04)

If you have customized such settings as Java heap settings, you must reapply your customizations after you install 9.04, as the settings are set to the SA default during installation or upgrade.



9.03

New platform support was added in 9.03.

For a list of supported operating systems and platforms for Server Automation Cores, Agents, clients, and Satellites, see the Server Automation Support and Compatibility Matrix .

9.02


Application Deployment Manager (9.02)

Application Deployment Manager benefits from two significant changes in HP SA 9.02. First,
Application Deployment Manager now integrates with HP Database and Middleware Automation
(DMA – formerly Stratavia Data Palette) through the DMA Flow Component. Second, application
definition has been greatly simplified with the introduction of a deployment debugger.

DMA Flow Component

Starting with SA 9.02, the new “DMA Flow Component” allows developers to leverage the vast
middleware capabilities of DMA to ensure the middleware requirements of their applications are
satisfied. For more information about DMA, see the DMA 1.0 User Guide. For more information
on configuring SA to use DMA, see the HP SA Integration Guide. For more information on DMA
Flow Components, see the Application Deployment Manager User Guide.

Deployment Debugger

The deployment debugger introduced in SA 9.02 allows developers to selectively execute
(or skip) components, include (or exclude) servers, step incrementally through deployments, set
breakpoints and pause on deployment failure. The ability to pause on failure allows developers to
investigate managed server state before rollback restores the systems to their last good state.
The fine-grained deployment job control allows developers to focus on problematic components
and more quickly produce a stable application version for release into production.

Approving Blocked Jobs (9.02)

Approving Blocked Jobs that Run SA Extensions

Job Approval Integration in SA allows you to block certain SA jobs from running until they
are verified and unblocked. The typical method of unblocking these blocked jobs is by using
HP Operations Orchestration (OO). SA provides a way to unblock jobs that run program
APXs (Automation Platform Extensions) without requiring HP Operations Orchestration.
For more information on Job Approval Integration, see the SA Platform Developer's Guide.

In releases prior to SA 9.02, the only way to unblock blocked jobs was by calling an OO flow.
The OO flow performed the appropriate checks and unblocked the job, allowing it to run.
SA 9.02 added the ability to verify and unblock jobs that run program APXs without requiring
HP Operations Orchestration.

NOTE: This applies only to "Run Program Extension" jobs, which are jobs that run a program APX.
APXs are extensions to SA. For more information on APXs, see "Creating Automation
Platform Extensions (APX)" in the SA Platform Developer Guide.


Starting with SA 9.02, you can create a specifically named program APX that will run without
blocking. This allows you to write a program APX that can unblock other APX jobs, without
the control APX itself being blocked. To specify an APX to unblock jobs, set the following
system configuration parameters in the SA Web Client.

System Configuration Parameters for an APX to Unblock Jobs Table

System Configuration Parameter

Script Running Order

approval_integration.apx.enabled

0 (default) disables the ability to unblock jobs
with an APX.
1 enables unblocking jobs with an APX.

 

approval_integration.apx.uniquename

Specifies the name of the program APX that will handle blocked jobs.

Enabling Job Approval for APXs

You must have the appropriate permissions to make changes to System Configuration
parameters. For more information on permissions, see the SA Administration Guide.

To create this type of APX, perform the following steps:

  1. Write a program APX that checks the blocked jobs and unblocks them using the SA API
    methods approveBlockedJob(), updateBlockedJob(), cancelScheduledJob() and
    findJobRefs(). These methods are the callbacks into SA that enable job approval
    integration. For details on writing APXs see "Creating Automation Platform Extensions
    (APX)" in the SA Platform Developer's Guide.

  2. Log in to the SA Web Client. For more information on the SA Web Client, see the SA
    User's Guide: Server Automation    .

  3. In the navigation pane, select Administration System Configuration. This displays the
    subcomponents of the SA platform.

  4. Under "Select a Product:", select Opsware. This displays the system configurations you
    can modify.

  5. Locate the entry for approval_integration.apx.enabled.

  6. Under the Value column, select the "Use value" button.

  7. In the text box next to the "Use value" button, enter a 1.

  8. Locate the entry for approval_integration.apx.uniquename.

  9. Under the Value column, select the "Use value" button.

  10. In the text box next to the "Use value" button, enter the unique name of your program
    APX that checks and unblocks blocked jobs.

  11. Select the Save button at the bottom of the page.

  12. Set up a mechanism to run this APX. For example, you could schedule this APX to run
    periodically to check for blocked APXs.

Disabling Job Approval for APXs

You must have the appropriate permissions to make changes to System Configuration
parameters. For more information on permissions, see the SA Administration Guide.

To disable the unblocking APX, set the value of approval_integration.apx.enabled to 0.
For details on setting this system configuration value, see Enabling Job Approval for APXs.

 

RPM Folders (9.02)

Restricting Access to RPM Folders

Starting in SA 9.02, you can ensure that your Linux managed servers only have access
to the set of RPMs in the SA Library that apply to each server. You simply specify in a
custom attribute the folders in the SA Library that the server has access to. All other
folders will be inaccessible to the server. This section describes how to set up these
restrictions.

With this new mechanism, you can mimic the common RedHat systems administration
paradigm of having multiple, distinct yum (Yellowdog Updater, Modified) repositories. This
gives you folder-level control over which versions of RPMs can be applied to a given server,
allowing you to precisely manage platform update versions, for example Red Hat Enterprise
Linux Advanced Platform Version 4 Update 5 versus Update 6.

This is not intended as a user-level access control mechanism, but rather to restrict the
library and folder view of a managed server from access to the full set of RPMs in the SA
Library. For information on user level folder access controls and folder permissions in the SA
Library, see the SA Administration Guide.

How the RPM Folder Restrictions Work

During remediation, if a server has one or more of these custom attributes defined, SA reads
the custom attribute values and only allows the managed server access to the RPMs in the SA
Library folders specified in the custom attributes and their subfolders. Subfolders of all the
specified folders are recursively searched for RPMs. All other folders are not accessible to the
server.


Enabling RPM Folder Restrictions

To restrict a server or group of servers to a subset of RPMs in the SA Library, set a custom
attribute in the format described below on your managed server or at a location that will be
inherited by the server such as a device group, a software policy, a customer, a facility and so
forth.

These custom attributes follow the custom attribute inheritance rules. For example, if you set
a custom attribute at the facility level, the servers in that facility will inherit the custom
attributes.

SA does not validate the SA Library folder paths you specify in these custom attributes so
make sure the folder paths you specify are correct.

For more information about custom attributes, see the SA User's Guide: Application
Automation.

Custom Attribute Format

The custom attributes that restrict access to RPMs must be in the following format:

repo.restrict.<name>

Where <name> is any user-defined alphanumeric string.
Specify a name that is descriptive and helps you remember the purpose of the
custom attribute. You can define multiple custom attributes as long as each
name is unique.

Examples:

The following defines custom attributes that grant access only to the SA
Library directories:

/Redhat/AS4/en/x86_64/U5 and /Oracle/10/AS4/x86_64:

repo.restrict.as4u5=/Redhat/AS4/en/x86_64/U5
repo.restrict.oracle_updates=/Oracle/10/AS4/x86_64

The custom attribute value can be multiple lines. The following defines custom
attributes that grant access only to the SA Library directories listed:

repo.restrict.as4u5=/Redhat/AS4/en/x86_64/U5 /Redhat/AS4/en/x86_64/U5-extras
repo.restrict.s5u3=/Redhat/5Server/en/x86_64/U3
/Redhat/5Server/en/x86_64/U3-extras
/Redhat/5Server/en/x86_64/U3-VT
/Redhat/5Server/en/x86_64/U3-Cluster

Sun Solaris Moves to Oracle (9.02)

As of the 9.02 release, Oracle and Sun were in the process of
retiring the SunSolve web site and establishing a new Oracle support web site
for Solaris patches and patch information. Once this transition is complete,
HP will provide information about how to modify your solpatch_import.conf
file to ensure that Solaris patching with SA continues to work correctly.
This information will be posted on the standard HP support channels.
For more information on Solaris patching and the solpatch_import.conf file,
see the SA User Guide: Application Automation.

For more information, see the Knowledge Base Article KM1032711 at:
(http://support.openview.hp.com/selfsolve)

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Fixed Issues for Previous 9.0x Releases

This section describes issues that were fixed in 9.0, 9.01, 9.02, 9.03, and 9.04. The table lists issues first by subsystem, then numerically within each subsystem.

 

QCCR1D QCCR1DSymptom/Description Platform

AAA

QCCR1D44941 SearchService.getObjRefs is returning non-readable object refs. Independent
QCCR1D116940

Cannot specify multiple LDAP servers for redundancy.

Support needed for external authentication redundancy for LDAP servers in twistOverrides.conf file.

 Independent

Agent

QCCR1D70222 Windows agents do not update their opswgw.args file. Windows
QCCR1D74021 The agent installer should detect when it is communicating with a new core. Independent
QCCR1D74339 Remove SSLv2 handshake from the Agent. Independent
QCCR1D98394 Scan button remains enabled when you enter an explicit negative IP address. Independent
QCCR1D111306 In some environments, output results from running the oglib.unix.unix_common.cmdCaptureBuf() script might be invalid. Unix
QCCR1D113666

Agent erroneously goes into revive mode on SA core components.

Resolution: To ensure that your core cloning operation is successful, before you create the clone, update the agent on the core to the version included with the 9.04 patch.

 Linux; VMware
QCCR1D114067 Agent Deployment dialog shows the following message when either the user name or password is incorrect:
"Deployment complete, 1 host succeeded, 0 failed" 		  Windows
QCCR1D114986 Search function produces invalid result. Independent
QCCR1D116227 Migration script output should be automatically placed into a log file. Windows Server 2008 R2 x64
QCCR1D120878 The agent crypto directory should not be readable by all users. Windows
QCCR1D121520 SA Web client returns an exception when you use an incorrect password during Windows agent deployment.  Windows
QCCR1D122051 In the SA Web client, range scans sometimes fail to scan complete address ranges. For example, the IP selection range  fails to scan addresses .251 .252 .253 .254 in the last octet. Independent
QCCR1D123048 Add support for AIX 7 as a managed platform. AIX
QCCR1D123098 Creation of a HyperV Linked Clone fails.  Windows Server 2008 R2 x64
QCCR1D129597 Agent installation fails for Japan locale when you install as a non-root user. Linux/Unix
QCCR1D129660 Network speed is reported as UNKNOWN for RHEL 6 x86_64.  Linux
QCCR1D129733 Add support for Citrix XenServer 5. Citrix XenServer 5
QCCR1D129953 Sometimes, you receive a return code of 128 when you run the .bat and powershell scripts on some Windows servers, even when the script runs correctly. Windows
QCCR1D129975 Agent cache fails to start, returning the following error: "Address already in use." Linux/Unix (supported for SA install)
QCCR1D130277 Enhanced MRL display and MRL selection confirmation requested for 2008 R2 Migration script. Windows Server 2008 R2 x64
QCCR1D130472 Agent does not start after it is installed. Win 2008, ESX 4.1, RHEL 5.6
QCCR1D131316 GUI reports a negative size for disk drives that are greater than one terabyte (TB). Solaris x86_64
QCCR1D131898 Agent upgrade replaces the R2 agent with a non-R2 agent. Windows 2008 R2
QCCR1D132110 In the Japanese locale, you might receive the following UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 15: ordinal not in range(128) Windows
QCCR1D132422 After running the Windows 2008 R2 migration script on a server, SA does not reflect its upgrade status when displaying the server information. Windows Server 2008 R2 x64

Agent Deployment/Upgrade - Backend

QCCR1D102401 Duplicate MAC addresses for certain devices prevent the agent from installing and prevent hardware registration. An error message like the following occurs: ERROR: spin.notUniqueInDatabase - More than one Server found with interface hw_addr '33:50:6F:45:30:30' Independent
QCCR1D108132 The Add Hypervisor Progress window displays an error message indicating that the job is completed and that the status of the job is failed. Windows
QCCR1D111496 The dormant Agent fails to connect to a core. Unix, Windows
QCCR1D111807 A Unix script with environment variables, which is run by SA, does not return the same values that run on the managed server. All Unix (AIX, HP-UX, Solaris, Linux)
QCCR1D111970 Agent Tools Python Opsware API Access fails to install on VMware ESX servers. VMware
QCCR1D113031 Control Panel of the agent installer displays 0 bytes. Windows
QCCR1D114142

Discrepancy between cpu_family reported by different Agents on the same hardware.

Unlike Windows, the cpu_family name reported by the Agent on Linux does not distinguish between 32bit (x86) and 64bit (x64) CPU family names.		 Linux
QCCR1D112564 Agent Install fails because of an Agent Gateway check fail. Windows
QCCR1D113351 Windows Server 2008 R2 does not display an OS Version in the server record. Windows Server 2008 R2
QCCR1D115710 C runtime library runtime error displayed by Opsware agent. Windows 2008 x64 and Windows 2008 R2
QCCR1D115849 When no options are given on the agent-installer command line, the -h option is not displayed in an error message. Independent
QCCR1D117436 Requested support for passwordless SSH for agent deployment tool (ADT) during agent deployment. Independent
QCCR1D117535 Agent reports the OS version as Linux Unknown instead of the correct OS version. OEL 4.4 i386 and OEL 4.4 x 86_64
QCCR1D117828 Requested agent installer support for filesystems larger than 2 Terrabytes. Unix
QCCR1D118171 Agent Deployment (including staging the Agent binary to the server through the WAN using SA push) is very slow.
 Independent

Application Configuration

QCCR1D61445 When parsing or applying CML templates, the parser exceptions are not helpful. One error included the error message "Error on line: Null". Independent
QCCR1D70119 When you click Save, the state of the editor will be lost and all nodes will be expanded. Independent
QCCR1D76553 The Undo action for the Configuration Template properties Content tab does not work. Independent
QCCR1D80888 The iis-web.tpl: encoding value from the .config file is overwritten by the Agent encoding value. Independent
QCCR1D106203 XML elements with single CDATA elements are not supported. Independent
QCCR1D111027 When loading an application configuration in a software policy, the application configuration must support all versions of all operating systems that the parent software policy supports. This does not apply to .zip files RPM's because they can support a single instance of RHEL, instead of every version the software policy supports. There is no parity between application configurations and virtually every other item in a software policy. Independent
QCCR1D111359 Comments and new lines in XML file are not displayed in XML preview even when the preserve format option is active. Independent
QCCR1D111558 Unable to create localization files from folder. Independent
QCCR1D111765 Unable to modify application configuration value sets for all scopes (Configuration Facility Customers). Independent
QCCR1D111819 Error message is incorrect after you set a previously scheduled job's date/time to a lapsed date/time. Independent
QCCR1D111851 Some servers fail during Configuration Compliance with an "integrity constraint" error. Independent
QCCR1D111992 The session_id in the compliance_summary table is null when running compliance for a software policy containing an application configuration. Independent
QCCR1D112119 The configuration table cell editor does not enforce character limitation and naming constraints. Independent
QCCR1D112121 The templates table cell editor does not enforce character limitation and naming constraints. Independent
QCCR1D113689 Looping occurs when previewing a file with a CML containing an unstable loop. Independent
QCCR1D114041 The Configured Applications tree does not get updated when attaching a software policy. Independent
QCCR1D114142 Discrepancy between cpu_family reported by different Agents on the same hardware.  Linux
QCCR1D114398 When attaching a software policy that contains an application configuration to a group, the Configured Applications tree is not updated. Independent
QCCR1D129446 Add the ability to disable snapshots during an application configuration push. Core

Application Deployment Manager

QCCR1D104590 Long strings resulted in errors. The length of string fields are now validated before writing to avoid Oracle errors or multi-master restrictions. Independent
QCCR1D107544 Double-clicking in the Type column for a parameter resulted in an empty edited dialog that caused an error when you clicked OK. Independent
QCCR1D109343 Deleting a version left an empty version folder in SA Library Independent
QCCR1D110134 You could create and start a deployment job using a target that contained an empty tier. The Jobs log reported that the deployment job was successful, even though it did not do anything. Independent
QCCR1D110852 When you create or modify a Software Policy, Software Package, or Application Configuration component, you can search for pertinent library items and then select the one that you want to use. Previously, if your search returned no items that matched the platform of the tier, there would be no indication why the search results table was empty. Independent
QCCR1D110875 “Save Changes” dialog appeared when there were no pending changes Independent
QCCR1D111038 On the Deployment screen, the following fields in the right panel should remain blank until you select a version and a target: Parameters, Changes, Comment, Rolling Deployment, and Scheduling. Previously, the settings used in a previous deployment editing session were not cleared. Independent
QCCR1D111103, 111128 When adding or editing a parameter, if you entered more than 4000 characters in certain fields (Name, Value, Description, or Target Value), a cryptic error message would appear when you tried to save your changes. Independent
QCCR1D111106

When exporting an Application Deployment Manager environment to a device group with targets that contained servers that had been deleted, you received the following error message:

“java.lang.RuntimeException: Unable to update the device group representing the target '[target name]': DeviceGroup or Server deleted during operation, try again.”

 Independent
QCCR1D111121 Server-specific special variables (such as Server Name or Server ID) and tier-specific special variables (such as Server names for Tier “Tomcat 6.0.20” or Server IDs for Tier “Tomcat 6.0.20”) should never appear in the list of available special variables used to define the values of parameters used by the Pre-Deployment and Post-Deployment flows for an environment. Previously, these special variables were available in this context. Independent
QCCR1D111218 When you selected an item on the Jobs screen, the items would be re-sorted, and the selected item would move somewhere else—possibly out of view. Independent
QCCR1D111223 If you attempted to create a new environment or modify an existing environment, and that operation failed, the Environments page did not refresh—which made it appear that your operation was successful when, in fact, it was not. Independent
QCCR1D111236 On the Applications screen, deleting a tier that contained one or more components disrupts other tiers. Independent
QCCR1D111325 On the Deployment screen, the tool-tip that appeared when you moused over the Select Target drop-down menu incorrectly displayed the name of the last selected target when the label displayed was “No Targets” or “Select Target.” Independent
QCCR1D111398 The Manage Targets dialog enables you to select multiple targets and move them from one group to another. Previously, only one item was moved. Independent
QCCR1D111500 A UI exception occurred when a user who did not have permission to Create Applications or Manage Application Deployment attempted to drill-down from the Jobs screen Independent
QCCR1D111507

“Server and policy platform mismatch” error occurred at deployment time when using tier policy. If the server platform did not match the platform of the policy associated with the tier, a deployment job was started, but it immediately failed. This was inconvenient, since the mismatch should have been reported earlier.

Resolution: You are now warned that the job will fail because the platforms do not match. 		Independent
QCCR1D111595

If you cancelled a job that had just started, the confirmation dialog contained a message that said:  “Are you sure you want to cancel job?”

Resolution: Confirmation message now reads, “Are you sure that you want to cancel the selected job?” if the job ID is not yet available.		 Independent
QCCR1D111656

Backup and rollback scripts for large Code components were failing, because the default timeout for these scripts was very short.

Resolution: You can now configure the timeout when you specify the Code component. The default setting is 3600 seconds (one hour). See “Code Components” under “Types of Components” in the Application Deployment Manager User Guide.		 Independent
QCCR1D111680

The Windows Backup and Rollback scripts were not handling directory hierarchies correctly. For full releases, the Windows Backup script backed up files into multiple places and created too many files when the Source Directory had subdirectories. For delta releases, it did not back up files in subdirectories correctly.

Resolution: Both the Backup and Rollback scripts now work correctly.		 Independent
QCCR1D111681

Windows backup and rollback scripts did not work properly if the drive letter was not specified for the Default Install Path.

Resolution: Application Deployment Manager correctly resolves the path, adding the default drive letter to the beginning.		 Independent
QCCR1D111926

The Parameters grid on the Deployment screen should show components like the Component Editor does so that you can see where parameters come from.

Resolution:  The Parameters panel on the Deployment screen now contains a Component column.		 Independent
QCCR1D111959

Parameter values were incorrect if an application included more than one OO Flow component.

Resolution: Parameters now have correct values no matter how many OO Flow components are included.		 Independent
QCCR1D112013

If two or more environments contained targets with identical names, the incorrect environment was sometimes shown in the Parameter Editor dialog.

Resolution: Application Deployment Manager now requires that all targets have unique names.		 Independent
QCCR1D112151

Application Deployment Manager did not warn users in the Job Step output when a Script component timed out. There was no indication in the Output area of the job Step details window that a timeout had occurred. This is the window that is displayed when you double-click a job step on the Jobs screen (or in the Debugger) or when you drill-down from the Job details window.

Resolution: The Output area in the job Step details window now indicates the reason that a Script component fails.)		 Independent
QCCR1D112597

Any SA job can be blocked pending approval. Application Deployment Manager deployment jobs are subject to this blocking. Previously, if an Application Deployment Manager deployment job failed because it was blocked pending approval, no message to that effect was displayed.

Resolution:  Application Deployment Manager now reports that the job is blocked and waits until it is either approved or disapproved.		 Independent
QCCR1D112941

When you used a special variable in a parameter to refer to a server, any output that contained the server name would show the SA name for that server, not the host name.

Resolution: Three new special variables were added: server.hostname, deploy.servers.hostnames, and {tier["<name>"].server.hostnames}. You can use these variables when you define parameter values.		 Independent
QCCR1D113127

You could add deactivated servers to a target, but you could not deploy to them.

Resolution:  You can no longer add deactivated servers to a target.		 Independent
QCCR1D113283

The Filter box in the Select Targets dialog enables you to show only those servers whose platform matches the selected version. Previously, if you selected the Filter box, and there were no valid servers to choose from, you would see a cryptic error message.

Resolution: If there are no valid servers, an empty tree is displayed.		 Independent
QCCR1D113342

The tar options used by Application Deployment Manager were not valid on all platforms.

Resolution: Code components can now be successfully deployed on all supported platforms.		 Independent
QCCR1D113382

The Backup step on Solaris platforms incorrectly reported “nothing to back up” when a backup was, in fact, performed.

Resolution: The Backup script for UNIX code components was repaired.		 Independent
QCCR1D113426

The file names in the Code component changes list were not sorted.

Resolution: The list is now sorted hierarchically (and alphabetically at each layer in the directory structure).		 Independent
QCCR1D113491

Long Application Configuration names did not display correctly in Application Deployment Manager.

Resolution: The name is now truncated to fit in the column. You can see the complete name in the tool tip that appears when you mouse over the name in the table.		 Independent
QCCR1D113603

The underscore character was not displayed in the Select Policy, Select Package, or Select OO Flow dialogs.

Resolution: This character is now displayed correctly.

Independent
QCCR1D113785

Previously, you could add the same user or group to the list on the Permissions tab for applications and environments.

Resolution: Users and groups that have already been added to the list are removed from the drop-down list of available choices.		 Independent
QCCR1D113823

The name of the “Revert” button is inconsistent.

Resolution: The name of this button is now “Revert [item]” in all contexts.

 Independent
QCCR1D113841

In the Edit Application and Edit Environment dialogs, there was no distinction between an individual user and a user group in the table on the Permissions tab.

Resolution: There is now a Type column that says User or Group

 Independent
QCCR1D113897

Previously, the Add Servers to Target dialog listed servers running ESX and servers in the “Unknown” OS category when you were adding servers to a Windows tier.

Resolution:  Only Windows OS servers are listed for Windows tiers; only UNIX servers are listed for UNIX tiers.		 Independent
QCCR1D 113911, 114664, 114856

Previously, if a job failed because the registry key was invalid, the job did not complete with failure status. All registry key names and values are now carefully validated when components are saved.

Resolution:. All registry key names and values are now carefully validated when you save the component.		 Independent
QCCR1D 113965, 115706 Previously, when a Code component was deployed with the Filesystem source type,  symlinks were not preserved or recreated on the targets. The symlinks are now preserved. Independent
QCCR1D114197

Searching for an OO Flow with no characters in the Search box failed. Previously, if you clicked the Search button in the Select OO Flow dialog, and you had not entered anything in the text box, the search would time out without returning any items.

Resolution: Fixed. This search matches full words in the OO Flow name. If you do not enter anything in the “Full word” box, you are now warned that searching without supplying a full word could take minutes. The timeout was also increased to 18 minutes. If no items are found that contain your search word, you now get a message to that effect.		 Independent
QCCR1D114666

Previously, binary registry key values in the Add Value dialog box were displayed as hexadecimal.

Resolution: Binary keys are now displayed in binary.		 Independent
QCCR1D114764

Previously, if you initiated roll back or undeploy of a version that was older than the most recently deployed version of the same application, you were not warned about or prevented from doing that. This is dangerous and strongly discouraged.

Resolution: Now, you are warned if you attempt to roll back or undeploy an older version. You must confirm your intention to proceed.		 Independent
QCCR1D114918

 In a Windows Registry component, if you specified the value of a DWORD type key using decimal characters, the key would not be created. Only hexadecimal characters worked.

Resolution: Decimal values are now converted to hexadecimal. DWORD type keys are now validated when you save the component.		 Independent
QCCR1D114921

If Application Deployment Manager was stopped, any deployment jobs that were running at the time never completed and appeared to be IN_PROGRESS in perpetuity.

Resolution: Fixed. If Application Deployment Manager stops and restarts, any deployment jobs that were in progress are examined to determine what action needs to be taken. If a job step was in progress when the ADM stopped, the job is marked FAILED and rollback is initiated. If all job steps were successfully completed, the job can be marked Completed.		 Independent
QCCR1D115117

Needed a horizontal scroll bar in the “Add Servers to Target” dialog. When you opened a hierarchy of Device Groups—such as Public : Opsware : Operating System : All Linux : All Linux Red Hat—you could not see the full names of the child device groups, because they were truncated and there was no horizontal scroll bar

Resolution: There is now a scroll bar.

Independent
QCCR1D115184

If you tried to update the server count for a rolling deployment, the count was reset to 1.

Resolution: Fixed. The server count is now updated correctly.

Independent
QCCR1D115204

A “Failure parsing template” error was reported after an Application Configuration was selected. When you selected an Application Configuration, if Application Deployment Manager failed to parse the template used with the Application Configuration, cryptic error messages were reported.

Resolution: The ADM now parses properly formed Application Configuration templates correctly. If a failure occurs, a more meaningful error message is displayed.		 Independent
QCCR1D115209

You were previously allowed to select the same Package more than once.

Resolution: You can only select a Package once.		 Independent
QCCR1D115367

An Incorrect Job ID was referenced in the confirmation message for rollback or undeploy.

Resolution: The correct Job ID is now displayed.

Independent
QCCR1D115368

If you scheduled a deployment job to stage immediately but cut over at a different time, and later changed your mind and modified the scheduled cut-over time to be on a different date, the time displayed in the “Wait for Cut Over Time” job step was different than the time displayed in the Reschedule Job dialog.

Resolution: The correct cut-over time is now displayed in both places.

Independent
QCCR1D115534

Previously, if you deleted a release, you could never use its name again.

Resolution: You can now recycle release names

 Independent
QCCR1D115546

ADM experienced memory issues when there were many Code component changes to show. When creating a new version of a full release, if you selected “Show Code Component Changes,” and there was a very large number of files included in the Code components, you might see cryptic “out of memory” error messages.

Resolution: The number of files in a Code component is now limited to 100,000 for a full release.		 Independent
QCCR1D115949

The Parameter Values dialog was not rendering correctly.

Resolution:  The Value field is now limited to 300 characters, and you can use the arrow keys to display additional characters.

 Independent
QCCR1D116465

When you created or modified a lifecycle, the list of Available Environments is not sorted, causing problems if numerous environments are listed.

Resolution: The list is now sorted alphabetically by name.

 Independent
QCCR1D116612

The following misleading message appeared in a pop-up dialog box after the job started when the“Show Jobs screen when deployment starts” option was not selected:

“One or more deployments have been scheduled. View results in the Jobs tab.”

This message is incorrect. At this point, the job is actually running and is no longer in the Scheduled state.

Resolution: The message now reads: “One or more deployments have been started.”

 Independent
QCCR1D116707

RPM and MSI packages were imported as type ZIP. The name of the “Import Package” tool used when specifying a Package component was confusing, particularly in the following scenario:

  • If an RPM or MSI file is added to a Package component using the the “Add Package” tool, that RPM or MSI file is copied to the “Default Installation Path” on the target server during deployment.
  • If an RPM or MSI file is added to a Package component using the “Import Package” tool, the ZIP file containing the RPM or MSI file is copied to the “Default Installation Path” on the target machine during deployment.

Resolution: The name of the button was changed to “Create ZIP Package from Files.”

 Independent
QCCR1D116759

On the Deployment screen, you should not be able to select a Target in an Environment that is not part of the Lifecycle associated with the specified Version.

Resolution: Now, only those Targets that belong to Environments that are part of the Lifecycle associated with the specified Version are available.

 Independent
QCCR1D116854

Symptom: Occasionally, the following refresh error message was displayed when the Step details dialog was open while a job was running, and the job failed:

“A data refresh failure has occurred. No further refreshes will occur.”

Resolution: The Step details window is now dynamically refreshed to reflect any status changes that occur until the job runs to completion.

 Independent
QCCR1D116867

When a non-superuser with View All Jobs permission, but no Create Applications or Manage Application Deployment permission, viewed a job that they did not own, the Job Steps and Parameters tables were empty.

Resolution: Both the Job Steps and Parameters tables now show the correct information for the job.

 Independent
QCCR1D116880

Automatic backup steps for some components were failing due to timeout errors.

Resolution: The timeout for backup steps was increased from 5 to 60 minutes.

 Independent
QCCR1D116883, 117774

In the case where an Environment contained some targets that were suitable for the specified Version and some that were not suitable, the Environment name was “grayed out” in the Select Targets dialog in the Deployment screen. This made it appear that no Targets in that Environment were available when, in fact, some were available.

Resolution: All Environments that contain suitable targets are now shown as available.

 Independent
QCCR1D117848

When you create a new deployment on the Deployment screen, the Stage selection should be “Now,” and the Cut Over time should be “Immediately” by default. Instead, the values from the previous deployment were selected—they were not reset.

Resolution: The correct default values are now selected.

 Independent
QCCR1D118052

Scripts were not consistently updated during a Patch Upgrade. Some “out of the box” backup and rollback scripts were not properly updated after an SA patch was installed.

Resolution: All scripts are now correctly updated when a patch is applied.

 Independent
QCCR1D118701

You could not add a Tier to an Application if the Tier name contained certain special characters. Specifically, the Add Tier dialog would appear completely empty.

Resolution: All characters except double-quotes (") are now allowed in Tier names.

 Independent
QCCR1D118746

After upgrading the Java plug-in for your browser to version 1.6.0_22, the following error dialog appeared whenever the SA Client or Application Deployment Manager is launched:

The new Java Plug-In requires a recent version of the FireFox browser (Firefox 3 or later)

Resolution: This error no longer occurs.

Independent
QCCR1D132376
(Enhancement)		 Code components install files into the "Default Install Path" specified in Application Deployment Manager UI. This enhancement adds the ability to force a directory prefix (called a Base Directory, and controlled by the Application Deployment administrator) for use in combination with the "Default Install Path" setting. Independent
QCCR1D132893
(Enhancement)		 Using Application Deployment and HP OO together, it is possible to both trigger Application Deployment jobs using HP OO and to have Application Deployment jobs trigger HP OO flows. Matching up log files from both products can be challenging. This enhancement adds logging of the Application Deployment job comment (which can be used as a marker when starting jobs from HP OO) and the ability to match Application Job steps to their parent jobs by logging the Application Deployment job ID with each job step. Independent

APX

QCCR1D112395 When you run a task fraction APX application of a server in the Solaris core, you receive a standard error notice. Solaris
QCCR1D117680

APX session timeout is not correctly implemented.

To increase timeout for Web APX Proxy (Note: this must be done at all the Slices on all the Cores):

1. Edit /etc/opt/opsware/apxproxy/apxproxy.conf to specify both the session timeout and socket timeout. Make sure socket timeout is at least equal to session timeout. For example,

apxproxy.apx.session.timeout=1200000
apxproxy.apx.socket.timeout=1200000

2) Edit both /opt/opsware/apxhttpd/conf/httpd.conf.tmpl and /var/opt/opsware/ogfs/mnt/root/opt/opsware/apxhttpd/conf/httpd.conf.tmpl to add a timeout directive. Add this property after the "Server" property. For example,

TimeOut 1200

Remember, unlike apxproxy.conf, the timeout value in httpd.conf.tmpl is in seconds, not milliseconds.

3) Restart the Core.

 Independent
QCCR1D122408 SA Web Client displays an error when you run a Web APX application. Windows

Audit and Compliance

 

QCCR1D55463 Hardware audit of CPU should include stepping to allow for CPU comparisons.. Independent
QCCR1D119274 The opsware.swprov.doer script does not function correctly for application compliance and controller semaphores. Independent
QCCR1D132059 Add the SA 7.82 audit-reporting capability to this release. Independent

Audit and Remediation

 

QCCR1D81358 There is "hex_ntop failed" data for a snapshot on IIS Metabase object. Windows
QCCR1D55465 It should be possible to flag Windows Registry audits as non-case sensitive. Independent
QCCR1D69863 Audits that have several hundred thousand audit results can cause the Web Services Data Access Engine (twist) to crash. Independent
QCCR1D89044 An audit run on a large number of servers (+150) may not complete successfully due to memory issues. Independent
QCCR1D92932 Snapshot specification job fails with a legacy exception on a Windows XP server.
The following error is displayed:
An error occurred during the audit.
Resolution Steps: Please see the additional messages for more information. If this does not resolve the issue, contact your Opsware administrator. Legacy Error Code: wayscripts.auditGenericError msg= All member snapshots in a Snapshot template failed.		 Windows
QCCR1D105021 The Audit Results browser contains miscellaneous, invalid characters (such as " : 0 ") that should be removed. Independent
QCCR1D105146 In the Audit Policy window, in the Properties Name, the text field should be enabled and prompt for input when you select New to create an audit policy. Independent
QCCR1D108616 When you rename an instance of compliance check, the new name displays in the lower pane, while the old (previous) name displays in the top pane. Independent
QCCR1D110611 A snapshot with the perform inventory option shows no warning to upgrade the Agent when selecting items that are not supported by an old Agent version (SMOs). Independent
QCCR1D110811 The compare .config file audit did not detect differences when comparing link files. Unix
QCCR1D111682 The View button and Contents panel do not display for the "Application Configurations" rule in the Snapshot Specification window. No application configuration rule can be added for the snapshot. Independent
QCCR1D111791 The stempcache directory is not automatically cleaned up when there is an audit failure. Independent
QCCR1D113305 Move Compliance view in Management Policies panel. Independent
QCCR1D116286 When renaming and saving an instance of a compliance check in the Audit Policy or Audit Task browser, the new name does not display when you reopen the browser. Independent
QCCR1D116514 Dataminer will not mine CIS 1.5 audit results. Independent

BSAE Integration
QCCR1D131229 Discovered Software reports are not setting the END_DATE parameter to the year 4000. Independent

Command Engine

QCCR1D71848

If the Command Engine is too busy or otherwise unavailable, PENDING jobs cannot be run, however, when the Command Engine is available again, the missed PENDING jobs run, regardless of how old they might be.

PENDING jobs now have a default limit of 600 seconds after which they are considered stale jobs and will not be run when the Command Engine becomes available again. (This limit is configurable but you must contact your SA Support Representative to change the default time.) For example, you have a one-time job that is scheduled to run at a future date and time. When it is time for the job to run, the Command Engine is down. When the Command Engine comes back up, the PENDING jobs are inspected, to check whether or not the job should run based on when the job was scheduled versus the current time, and if too much time has passed (600 seconds by default), the job is not run.

 Independent
QCCR1D117552 Add HP-UX patching support for HP-UX 11.11. HPUX 11.11

Command-Line Interface
QCCR1D118249 Failed to upload a package with Chinese name. Windows 2008

Core

 

QCCR1D109998 Multimaster conflicts are created when creating OS Installation Profiles for RHEL ES 3 or SunOS 5.9 under very specific circumstances. RHEL ES 3, SunOS 5.9
QCCR1D112878 The pytz library is not usable from an APX due to root-only file privileges.

Independent
QCCR1D116991 Debugging files are unusable. Solaris
QCCR1D117105 At least two Python C modules fail to compile for reentrancy. Solaris

Custom Fields

QCCR1D70320 Searching for servers using custom fields as search parameters in the SA Client, the SA Web Client, and the Command Center browser can return invalid results due to incorrect filtering. Independent

Data Access Engine

 

QCCR1D67030 When the Data Access Engine exceeds 1024 connections, too many files open errors occur. The connection limit for the Data Access Engine should be increased to 65536. Independent
QCCR1D116939 Installing satellites on Linux boxes fail if the boxes contain slices that are running SunOS 5.10. Data Access Engine (spin) fails to link against the libiconv_plug. Solaris

Database Scanner for Oracle (Storage)
QCCR1D123008 In order to monitor an Oracle 11G database with the SA Oracle Database Scanner, the XML DB and DBMS_NETWORK_ACL_ADMIN package must exist in the database.  The SA Oracle DB Scanner needs access to these objects in order to grant privileges and access for itself. If the objects do not exist, then the "pamuserprivilege.sql" script cannot complete its tasks and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database. Independent

DCML Export Tool (DET)

QCCR1D91664 DET should export only the ValueSets associated with an Account, instead it exports all ValueSets included those of associated customers Independent
QCCR1D92144 Import of OS Sequences populates incorrect flags in certain fields. Therefore, after OS Provisioning completes, software remediation jobs do not start and the build fails. Independent
QCCR1D119058 The Export Tool fails to export the /RAID Policies folder. Independent

Device Groups
QCCR1D111106 When you export Application Deployment Manager Environment to a Device Group
you receive the following error message:
"java.lang.RuntimeException: Unable to update the device
group representing the target '[targe name]': DeviceGroup or Server
deleted during operation, try again." 		Independent
QCCR1D111582 A null-pointer exception is logged to the java console when you selects a device in the Dynamic Group Device Membership content pane. Independent
QCCR1D120093 Device Groups cannot parse customer names that include commas. Independent
QCCR1D122303 Dynamic Group permission issue does not allow you to view device members. Independent

Extensible Discovery

QCCR1D110987

The get_firmware.sh script does not apply to SuSE 10 SP3 PPC64.

The Extensible Discovery get_firmware.sh script does not support the PPC64 platform.

 SLES10 SP3 PPC64

Global File System/Shell Backend

QCCR1D58417 The Global File System (OGFS) cannot be stopped properly because it cannot be unmounted and the host must be rebooted before the OGFS can be started again. Solaris
QCCR1D71625 When a customer, facility, or device group is deleted, all resource settings on either a user group or an OGFS privilege which references that object should also be removed. When they are not, the command cat loginToServer fails with an Input/Output error. Independent
QCCR1D110903 Server browser shows error "500 OGFS view dir does not exist SA". Windows managed server with locale set to S-Chinese (Code Page CP936)
QCCR1D112418 The following error occurred in "module" unix due to a NULL pointer: BAD TRAP: type=31 rp=2a103a81400 addr=0 mmu_fsr=0. Solaris 5.10
QCCR1D112419 unresponsive cycle in blocking chain. Solaris 5.10
QCCR1D116994 Core becomes unusable when you attempt to access long file names in the Global Shell (OGSH). ogsh. Linux
QCCR1D117781 Under certain circumstances, Global Shell functions slow down. Independent
QCCR1D122265 Add the ability to disable stream logging across all cores. Core

Installer

QCCR1D76655 Make get_slice_ips.py more user friendly. /opt/opsware/oi_util/bin/get_slice_ips.pyc was designed as a tool to be used internally by the Installer and, as such, was not prepared for the types of errors a user might introduce. When problems occurred, it responded with vague errors that were not helpful Linux/3AS, Linux/4AS, Linux/5Server, SunOS
QCCR1D130678 Certain syncbot packages that are still bundled as part of the distribution are no longer relevant and should be deleted. Independent

ISM Tool

QCCR1D92201 When using the ISM tool to build and upload an ISM package on a Windows managed server (using the ZIP package engine) and a configuration control script for access to custom attributes, the environment variables ISMLIB and ISMRUNTIMEDIR are not set to the correct paths. Windows
QCCR1D110511 ISMtool failed to upload ISM into a software policy. Windows Server 2008 (x86)
QCCR1D111304 Information about the created ISM shows supported platform as 'Windows 2000" instead of "Windows Server 2008 R2 x64". Windows Server 2008 R2 x64
QCCR1D111662 ISMControl does not work on Windows 64bit systems for ISMs built using the ZIP package engine. Windows 2003 x64, Windows 2008 x64, Windows Server 2008 R2 x64

Jobs and Sessions

QCCR1D111800 The server count is shown as zero ("0") when there is one server present in an Application Deployment job. Independent
QCCR1D111802 Application Deployment Manager job groups sometimes stop refreshing in the user interface. The refresh rate is also too slow. Independent
QCCR1D111856 Application Deployment Manager Job Group display is incorrect for Run Program Extension. Independent
QCCR1D117956 Custom Range filter not working correctly .in the Jobs and Sessions and History pages of managed servers. Independent

Microsoft Hyper-V

QCCR1D97630 In a multi-master mesh environment, simultaneous invocations of scheduled periodic scans on hypervisors can cause multi-master conflicts. These scheduled periodic scans on hypervisors are triggered by the SA user "virt_scanner". Windows

Model Repository

QCCR1D83813 Unable to sync differences in ServiceInstances after a referenced device has been deleted. Independent
QCCR1D91064 Oracle (10g) setup for the Model Repository requires that certain Oracle patches also be installed. These patches are installed automatically during an HP-supplied Oracle database installation. However, the patches must be manually supplied if you are using the Oracle Universal Installer to install the database or are using an existing Oracle 10g database. Independent
QCCR1D93757

Oracle RDBMS 11.1.0.7
Database user TRUTH statistics collection job fails with error: ORA-01000: maximum open cursors exceeded.

This error is intermittent and not all customers will run into this issue. The error is caused due to an Oracle bug (#7651092).		 Independent
QCCR1D96568

When duplicating a zip package, the package is duplicated without the path and the following error message is displayed:

You do not have permission to view details of this policy item.

 Independent
QCCR1D132776 Oracle database becomes unresponsive during an audit results calculation. Independent

OS Provisioning

QCCR1D65480

Import Media script should support long filenames for SMB.

It is difficult to translate long filenames to 8.3 syntax format when there is no unique naming capability in the directory structures. It takes a long time to translate these paths into the 8.3 syntax.		 Independent
QCCR1D71989 During Linux OS provisioning using a Software Policy and remediate pre-action and post-action scripts, the job fails when the Pre-Action script runs. All further Remediation steps are skipped and do not complete. Linux
QCCR1D88820

The version of the Samba server installed on the remote host during Linux OS provisioning has problems with securing the environment and should be upgraded to a secure release.

 Linux
QCCR1D89108 An error in the OS Provisioning job is not shown in the Job Status Error tab. ESX, Linux, Solaris, VMware, Windows, Windows 2000, Windows 2003, Windows 2008, Windows XP
QCCR1D93849

In a core where the value for truth.dcNm is not the same as the value for truth.dcDispNm, or truth.dcDispNm is not specified in uppercase only, Linux reprovisioning becomes interactive and prompts the user for the language, locale, etc.

Both thetruth.dcNm and truth.dcDispNm parameters were set during core installation.		 Linux
QCCR1D93881

You can upload an unattend.xml file that exceeds the maximum size allowed.

 Windows 2008
QCCR1D95401

The autoprovision for registerManagedNodeForDS would always send kickstart information through eth0.

If the server being provisioned has multiple network cards, SA may not consistently use one card throughout provisioning, which may cause provisioning failures.		 Linux
QCCR1D109925 winpe-ogfs booted servers were listed in the data error fail test. Windows
QCCR1D101920 Solaris 10 SPARC OS Provisioning job completes with the status Success, however the output in the client shows a Solaris 10 packages partially installed message. Solaris
QCCR1D102449

If you attempt to specify the Windows Server 2008 R2 volume license product key information by using the SA ProductKey custom attribute for Windows 2008 R2 OS Provisioning, the Windows setup process fails with the following error

The unattended answer file contains an invalid product key. Either remove the invalid key or provide a valid product key in the unattended answer file to proceed with Windows Installation.		  
QCCR1D103377 The following prepdisk error occurs on some Linux installs: "prepdisk.py failed: Incomplete arguments". Linux
QCCR1D107141

Run action is enabled in the OS Build Plan window for a user who does not have the "Allow Execute OS Build Plan" privilege.

You can select Action > Run when you do not have the required privileges.		 Independent
QCCR1D110077 Removing steps from the OS Build Plan causes a Null Pointer Exception (NPE). Windows 2003, Windows 2008
QCCR1D111245

The configuration value: bm.reprovision_attributes_to_preserve should default to change to a new value, rather than keep the old value.

If you locally change (overwrite) the value of this system configuration parameter in the SA installation, the upgrade process will preserve the value. This is often the correct behavior, but in this specific case the correct behavior would be to overwrite the data with the new data shipped with the SA product.		 Linux
QCCR1D111445 Run OS Sequence does not escalate device group privileges. Independent
QCCR1D111845

Provisioned machines using MBC may continually reboot into the un-provisioned server pool after initial provisioning because the sequence_id and MAC link were not removed.

 Linux
QCCR1D113004 Remediate job using OS Build Plans failed intermittently in cross mesh test. Windows 2003
QCCR1D113056 import_media does not correctly detect the .wim image URL. Windows
QCCR1D114303 The monitorServerBuildInit is never executed for OEL and CentOS. OEL 4, OEL 5, CentOS 5
QCCR1D114403 Mini-root shipped with 7.80.03 causes kernel issues during server provisioning with ZFS. Solaris 10 U6
QCCR1D114962 Requested removal of DOS Boot Install Type for New Windows OS profiles and Modify OS profiles. Windows
QCCR1D115542 No network adapters are displayed in ipconfig file when provisioning a DL580G7 server with a CN1000E card that uses the integrated Windows PE 64-bit boot image.
Support for HP StorageWorks CN 1000E (10Gb Ethernet) network cards requested.		 Windows
QCCR1D117873
/117885		 During Windows provisioning, if a driver is not present, the WinPE image does not recognize the NIC card. Windows
QCCR1D117508 Changes to Script Timeout are not saved if you reopen the OS Sequence. Independent
QCCR1D117509 Script output to export is limited to 10K for pre- and post-remediate scripts that are attached to an OS sequence. Requested: allow textbox in UI for flexible output size. Independent
QCCR1D117604 Gain control over options in the Remediate Policies job spawned by an OS Sequence. Independent
QCCR1D117669 When you select servers in the job-progress section during an OS sequence run, the Details pane window closes. The correct behavior is a selection change. Independent
QCCR1D119424 SA now supports NFS mount-option parameters (through the custom attribute nfs_opts) for any NFS mount options that can be specified in /etc/fstab. Independent
QCCR1D120085 The OS Provisioning configuration APX displays a "file or directory not found" exception. HP-UX
QCCR1D122206 The build script cannot verify that the second-stage installer matches the requested OS version. RHEL6 x86 and x86_64
QCCR1D122248 Reprovisioning fails for RHEL 6 that contains an ext4 file system. Linux
QCCR1D122490 ESX 3.x OS Provisioning breaks with missing parameter "ks_mandatory" Windows
QCCR1D122502 During software provisioning, you receive the following error:
No network information available from computer because there is no network adapter.		 Windows
QCCR1D122522 The buildmgr process might run out of file descriptors if TCP connections are made to port 1017 from a server that is still being tracked by the buildmgr process.  Linux
QCCR1D122845 The Windows_2008_R2_fix_script.pyc upgrade script does not run correctly. Windows Server 2008 R2 x64
QCCR1D129492 Winpe image does not contain vmxnet3 drivers. Windows
QCCR1D129588 OS Provisioning fails on OEL and CentOS. OEL 4,5 i386 and x86_64 ; CentOS 5 i386 and x86_64
QCCR1D129840 The import_media command fails. Windows 2008 R2 SP1
QCCR1D129925 During CD boot up, SA erroneously displays an interactive interface. RHEL6 SoS
QCCR1D130053 The Run OS Build Plan job launches, but with a negative job reference. Windows
QCCR1D130420 The manage_boot_clients_script randomly creates Manage Boot Client utility (MBC) records using the SHORTNAME value instead of the fully-qualified domain name (FQDM) value. Windows
QCCR1D130517 Add Jumpstart support for the Oracle/Sun T3-1 server. Solaris 10 SPARC
QCCR1D131268 During DHCP-less provisioning, SA erroneously displays an interactive interface. RHEL 3,4,5,6
QCCR1D131574 Winpe image does not contain the following disk driver: BL465c G7 - SAN card: Emulex FcOE NC551i. Windows
QCCR1D132345 Trying to boot an IA64 server from a boot cd causes  kernel issues. Linux
QCCR1D132353 When performing OS Provisioning from a Red Hat Enterprise Linux 6 host, if the media CD is mounted, Red Hat 6 will load Stage 2 images from the CD even if  an NFS share for the images has been specified in the kickstart.cfg file. Red Hat 6 (x86 & X64)
QCCR1D132504 Invalid Parameters error occurs while uploading packages. ESX4
QCCR1D120084 A compliance scan fails because the SA Repository has both a deleted and an active software catalog. HPUX
QCCR1D120773 Incorrect number of non-compliant patches displayed. HPUX

Patch Management

QCCR1D82708 If your system locale is set to GB (0809), Microsoft Windows patches are not displayed correctly in the SA Web Client. Windows
QCCR1D91986 Exception (not error) generated when editing the name of a Windows Patch Policy if the name already exists. Windows
QCCR1D92124 The Manage Windows Patch Policy READ privilege allows users with inadequate privileges to change the availability of Windows and Solaris patches. Solaris, Windows
QCCR1D95545 If you start a remediation under the following conditions, the server will not reboot:
* Reboot specified by individual software items.
* Patch products with reboot specified during install and uninstall.		 HP-UX
QCCR1D95745 When resolving the dependencies for a set of Solaris patches in a patch policy, the incompatible patches dialog may repeatedly be displayed. This can occur when an incompatible patch is required by another patch in the patch policy or when an incompatible patch obsoletes another patch in the patch policy. After you specify an incompatible patch to be removed from the policy, it may get added back because it is required by some other patch in the policy, resulting in the incompatible patches dialog being redisplayed. Solaris
QCCR1D110273 Patch installation fails for AIX 5.3 for EMR3 Agent 32h.0.0.101 without a specific error message; After the Agent is upgraded, the patch installation is successful. AIX
QCCR1D110313 In Advanced Search, there is a misspelled word in the Patch "Where" drop-down list. Sun OS 5.01, 5.10 x86, 5.9, 5.8, 5.7, 5.6
QCCR1D110340 Remediate shows a "Will Not Install" status for "Always Install" exceptions for a different platform than the managed server when the "Always Install" exception is at the server group level. Any platform that is not the same as the managed server
QCCR1D110391 Windows Server 2008 R2 patches are displayed in the patch library as Windows Server 2008 (x86) patches. Windows 2008
QCCR1D111862 Remediate of managed server with a group "Never" exception and a device "Always" exception causes a non-install due to the "Never" exception. Windows
QCCR1D111964 Incorrect tool tip for patch compliance when the patch is in the list of installed patches, has the “Never Install” exception set, and is not in a patch policy. Windows
QCCR1D112336 The solpatch_import create DB command fails for a DVD image on a fresh core install because the solpatch+import dir does not exist in /var/opt/opsware/. Solaris
QCCR1D114337 Windows patches that have more than 6 digits in their KB numbers do not have correct unit_name and unit_display_name values in the recommended_patches and installed_units tables. Windows
QCCR1D114417 If the custom attribute is not set, SA is unable to remediate some patches. HP-UX
QCCR1D115331

SA is not rebooting a server when remediating a patch that requires a reboot.

 HP-UX
QCCR1D117667 Text for a patch-installation message that is scheduled for a specific time is truncated. Windows
QCCR1D112588 The Add to Patch Policy option should be enabled when a Solaris patch or patch cluster is selected from Library > By Type > Patches > Solaris > SunOS 5.x. Solaris
QCCR1D113591 On June 4, 2010, Oracle changed the process of tagging patches as “'recommended”. After June 4, 2010, only the first patch to fix a Sun Alert issue is tagged “recommended”. Before June 4, 2010, the behavior was that the latest patch to include the fix would be tagged “recommended” and the “recommended” tag would be removed from the obsoleted patch. Sun OS 5.01, 5.10 x86, 5.9, 5.8, 5.7, 5.6
QCCR1D116919 RPM remediation fails for some remediations that include a mix of install-only and upgrade RPMs. Linux
QCCR1D117667 Text for a patch-installation message that is scheduled for a specific time is truncated. Windows
QCCR1D120083 Receiving traceback during script execution. HPUX
QCCR1D129593

Remediation of RHN imported policies may fail with dependency errors.

 Red Hat Platforms
QCCR1D129995 The AIX and HPUX patch UIs erroneously display the same fields as the Solaris patch UI.  AIX, HPUX
QCCR1D131100 When you run the solpatch_import script you receive the following error:
"Global name 'DEFAULT_PATCH_SIGNED_URL' is not defined."		  SunOS
QCCR1D131683

In rare cases, running the R2 migration script does not result in supplemental patch database migration.

Resolution: Migrate the supplemental patch database manually, or call HP Support for more information.

 Windows Server R2 X64

Power Shell Integration
QCCR1D88778 Character properties are not displayed when you run a powershell script. Windows 2008

Product Functionality

QCCR1D131363

Script output not displayed correctly for a script that echoes special characters on a I18N windows server.

 Windows

SA Client - Framework

QCCR1D81123 There are other HP rebranding items for a future release. Independent
QCCR1D91685 A new, saved search does not display in the drop-down selection list. Independent

SA Command Center Framework
QCCR1D130081 On some occasions, the Data Access Engine (spin) and the Command Engine (waybot) processes consume multi-gigabyte RAM resources. As a result of this increased consumption, the processes can bind the CPU and the Web Services Data Access Engine (twist) runs out of heap space and must be restarted.  Windows

SA-OO Integration

QCCR1D111738 When a Run Flow job for SA-OO Integration fails, due to a timeout in SA, the "Open report in HP Operations Orchestration" menu action displays as selectable, gray text. When you select this action, a "Cannot redirect to Operation Orchestration" error message displays. Independent
QCCR1D111740 Ticket_ID is automatically filled for Run Flow Job. Independent
QCCR1D112466 Flow integrations informational text says "Job Approvals", instead of  "Job Blocking". Independent

SA Web Client

QCCR1D111394 If the existing user group has OGFS privileges for multiple users/logins, not all OGFS privileges for multiple users are copied to a cloned user group. For example, if a user group that is going to be cloned has OGFS privileges, the user group clone will work only if the privileges are for one user/login. If there are multiple users/logins for a privilege, only one user/login privilege is copied into the new cloned group and the rest of the users/login privileges are ignored Independent
QCCR1D114769 Allow the ability to grant Global File System privileges in the SAS Web interface when the username contains a dash (-).  Independent
QCCR1D117501 When performing an OS profile edit and uploading a kickstart configuration or an unattend.txt file, the second upload remains in the initializing state, even if the entire upload is completed. Independent

SA Visualizer
QCCR1D94138 Found "Error Running SiteMap" in the user interface for an HPUX11iv3 with multiple SAN devices and switches connected. HPUX 11.31
QCCR1D110100 A question mark (?) icon displays for Cent OS after a scan. CentOS

SE Connector

QCCR1D93316 When you are creating a new access control, if you type the SE user name in the wrong case (SE is case sensitive about usernames) and then try to edit the SE Scanner access control to change the case (such as from lowercase to uppercase or vice versa), the changes are not implemented in the access control. This occurs when the user name contains all of the same letters and numbers as the user name that was originally entered, but only the case of the letters has changed. Independent

Search

QCCR1D117830 Search error (" The query was malformed or incomplete.") is received when you run two advanced searches in two different user interfaces, when one of those searches was opened from within the first user interface. Independent

Server Groups - UI

QCCR1D105997 For the following details panes, the title of the details pane should be the name of the selected View, but instead is the name of the selected Device group: Archived Audit Results, Device Groups, Hardware, Network, Installed Packages
 Independent

Server Management

QCCR1D106017

Panel title for the Inventory > Disks view displays incorrect title - it displays the server name.

 Independent
QCCR1D115884 UI issue: The Servers and Device Groups section of the Reboot Server task window incorrectly displays all reachable Windows servers, instead of displaying only the selected Windows server on a scheduled or completed job. Independent
QCCR1D117952

Improper display of multibyte characters when using IIS and COM+ on Korean servers

 Windows
QCCR1D122377 When you run the RHN import command /opt/opsware/rhn_import/bin/rhn_import -v –debug, the command fails to retrieve the RHN Channel list and you get the following RHN error:
You do not have permissions to perform this action.		 Core Platforms
QCCR1D129958 MAC address field is empty in the Server Browser > Information > Properties window. Windows 2008 R2 SP1
QCCR1D130573 Search function produces invalid result. Independent

Server Module

QCCR1D88807

IIS - Inventory fails on Italian/German/Korean/Japanese managed server using IIS SM.

IIS 7 SMO is failing because the xml.dom.minidom.parseString could not handle the output returned after executing the appcmd command in DOS for retrieving the values.		 Windows Server 2008
QCCR1D91597 When run on VMware ESXi servers, server modules give a false and, potentially, alarming error message. VMware ESXi
QCCR1D107867 The remediation of features from "Site" and "Application" Level is not implemented in IIS 7 SMO. Only the features from the "Web Server Level" supports remediation Windows Server 2008
QCCR1D111503

Remediation of Test sites does not copy all values from the source to the target.

Machine Key and Providers features are implemented in IIS7 SMO only for the "Web Server Level". The "Site Level" does not support these features		 Windows Server 2008
QCCR1D111521 SMO_Users and Groups - Failed to add a user to the target on Windows 2000 during a remediate operation. Windows 2000
QCCR1D112489

Environment verbs should not be evaluated.

Some parts of the IIS7 server module evaluate %WINDIR% as C:\Windows when auditing various settings (and/or content), causing mismatches when performing audits		 Windows Server 2008
QCCR1D112529

IIS7 Server Module audit and remediation issue with several applications in the application pool.

The "Number of Applications" contained in an "Application Pool" is a read-only column and should not be included in remediation for an Application Pool		 Windows Server 2008
QCCR1D113052 Remediation of an error page without subStatusCode creates an error page with subStatusCode=0 on the target. Windows Server 2008
QCCR1D113804 There is no distinction between remediation of providers feature from Web Server-Level and remediation of providers from Site-Application Level. The first uses the root path for setting providers, while the second uses the path of the Site or Application. Windows Server 2008
QCCR1D119945 Add RHEL 6 X86_64 to SMO support. Independent
QCCR1D119946 Add RHEL 6 to SMO support. Independent

Software Management

QCCR1D74750 A race conditions occurs during certain remediation jobs requiring retries and multiple remediate attempts. Independent
QCCR1D83256 In some cases, an incremental CBT import of an application policy that adds application configurations to the policy does not import the changes. Independent
QCCR1D83916

During Preview/Remediate, when there is insufficient disk space under /var directory, the following error should display:
insufficient disk space
However, this error is actually displayed:
The request to retrieve information from the Opsware Agent failed for an unknown reason, please contact your Opsware Administrator.Execution error:
Traceback (innermost last):
File "./base/wayfuncs.py", line 133, in evaluator
File "<string>", line 1212, in ?
File "<string>", line 1174, in main
File "<string>", line 586, in installPCA
File "<string>", line 382, in findTmpdir
AttributeError: debug

 Independent

QCCR1D102109

When attempting to remediate a Linux server, the operation fails with an error such as:
The remediate operation cannot be performed because an error occurred during preview.
/var/opt/opsware/yum/cache/opsware/repomd.xml:9: parser error

 Linux
QCCR1D111793 When there are Remediate job option settings changed after previewing, you cannot preview again. Independent
QCCR1D111861 After you add or delete policy items in a software policy and then save them, you are subsequently unable to open the software policy. There are Null Pointer Exceptions (NPEs) in the Java console. You must log off and then log back in to the SA Client. Independent
QCCR1D112589 Cannot add a Solaris patch to a patch policy from the patch's Patch Policies view. Solaris
QCCR1D112702 The popup menus for a folder in the folder tree are enabled differently, compared to the folder list. Independent
QCCR1D114781 A Null Pointer Exception (NPE) occurs when attempting to perform a remediation of a simultaneous attachment and detachment Independent
QCCR1D117057 Ad-hoc scripts are not executed on a multimaster environment. Independent
QCCR1D120520 There is a mismatch between the total number of filesets within a bundle and the number of filesets SA reports in the Compliance tab. HP-UX
QCCR1D131569 When using a parent folder with more than 1000 subfolders, the Repo.restrict script throws the following exception: ORA-01795.  Independent
QCCR1D131703 If you remediate a software policy that was already remediated, SA uninstalls the RPM and its dependency. Linux

Software Repository

QCCR1D99828 A cascading satellite (an SA satellite whose gateway is connected to another satellite's gateway rather than to an SA Core Management Gateway) cannot connect to the Software Repository cache of another satellite due to a certificate error. Independent
QCCR1D121952 Satellite cache cleanup fails when it finds a package it cannot identify. Linux
QCCR1D129410 Oupload process fails and displays the following error when uploading a Lightweight Presentation Protocol (LPP) file:
"Invalid LPP file" error.		 AIX
QCCR1D129666 A garbage collection job in the Software Repository (word) fails to function correctly and results in the accumulation of an excessive number of Data Access Engine (spin) requests, impacting performance and resulting in the accumulation of an excessive number of garbage data in the database (truth). Independent
QCCR1D130116 Unable to upload custom Solaris patch clusters. Independent

SSL - Secure Environment

QCCR1D83898 A scan on port 1028 found the following issue: "SSL Server Allows Cleartext Communication (NULL Cipher Support) This host is running an SSL server that supports NULL cipher. The NULL cipher is a 0-bit SSL connection that does not provide encryption; any network traffic is in plain text. Solution: Disable the NULL cipher. Reconfigure the SSL server to provide suitable encryption." Independent

Storage Host Agent Extension

QCCR1D100922

When an HPUX 11.23 server is presented with a LUN via dual port HBA, the user interface shows only one FC target mapping.

The NGUI panel Inventory>Storage>Volumes>[Select Access Path View]>Select a LUN presented via dual ports HBA, the bottom panel will show only one target mapping instead of two entries. This occurs when an HBA driver does not support the SNIA HBA 2.0 version.		 HPUX 11.23
QCCR1D101464

For LUNs managed by Solaris Native MPXIO, the multipath count is displayed as 1. This behavior is seen on Solaris versions before Solaris 5.10 Update 3.

For Solaris versions before Solaris 5.10 Update 3, the Storage Host Agent Extension inventory snapshot specification fails to discover the information related to Solaris Native MPXIO software. Because of this, MPXIO managed multipathed LUNs will have their path count as 1.		 Independent
QCCR1D109306 The supply chain breaks when users create multilevel LVM RAID volumes, such as RAID10 or RAID50, and the Inventory > Storage > Volumes panel does not display supply chains for multilevel-RAID volumes. Linux

UI (DSE)

QCCR1D117600 Severe java-console error occurs when you run a server script on a Device Group. Independent

Virtualization

QCCR1D71640

When an imported LDAP user clicks the Next button in the Create Virtual Zone wizard's Zone Definition step, they do not advance to the next step. The following NullPointerException error is returned:

WARNING init(NguiUser:-1): No user date format specified, using JVM defaults
java.lang.NullPointerException
at com.opsware.ngui.virtual.task.ZoneDataSpecificationPanel$
ServerVirtualizationZonePanel.createPanel(Unknown Source)
......
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)

at java.awt.Container.dispatchEventImpl(Container.java:1613)		 Windows
QCCR1D71995 The progress bar does stop after opening a Virtualization object browser. Independent
QCCR1D77903 Unable to modify a virtual machine's storage with add and remove operations in the same job. ESX, ESXi
QCCR1D78017 The ManageEsx create command fails with a Null Pointer Exception (NPE). The command was replaced with a shell script. Linux/3AS, Linux/4AS, Linux/5Server, SunOS
QCCR1D80218

When more than 2 GB memory is allocated for Local Zones, requests for memory information causes Web Services Data Access Engine errors.

 Solaris
QCCR1D81233 When you open Create/Modify/Remove virtual machine jobs whose server has been deleted, an NPE error displays. Solaris, Vmware, HyperV
QCCR1D81241 A deleted hypervisor server is displayed as "null" in completed Create virtual machine and Remove virtual machine jobs. Solaris, VMware, HyperV
QCCR1D83717 The Create Virtual Machine wizard, does not allow creating VMs with Windows Server2008 or Red Hat Enterprise Linux 5. Windows Server 2008/Red Hat Enterprise Linux 5
QCCR1D92213 ESXi edit connection events should be logged in the history log file. Independent
QCCR1D92216

Update ESX VMM code to version 2.5.

SA should take advantage of latest enhancements and features such as cloning		 ESX, ESXi
QCCR1D93224

A completed Create Virtual Zone job does not show the zone creation command script.

SA did not initiate a scan of the hypervisor after a successful edit connection. You must perform a reload data action.		 Solaris
QCCR1D92336 ESXi Edit connection: No HV scan is performed after a successful edit connection. Independent
QCCR1D93612 Creating a virtual machine with auto-provisioning and multiple NICs did not allow you to specify which NIC must be used as the provisioning device. ESX 3, ESX 4, ESXi 3, ESXi 4
QCCR1D93686 Suse64Guest is missing from the list of guests that require the E1000 adaptor. Independent
QCCR1D93713 Create Virtual Machine: The Job Status view is inconsistent between the live view and the view you get when opening the job from the history view. Independent
QCCR1D93764

ESXi hypervisor in maintenance mode: You cannot create virtual machines when it is not allowed.

Hypervisors in maintenance mode that were the targets of any VMM operation would fail with an unrecognized error.		 ESX 3, ESX 4, ESXi 3, ESXi 4
QCCR1D104418

The reported OS property for ESX servers is inconsistent between direct (SA Agent) and indirect managed (vCenter) cases.

Hypervisors previously included in a device group, based on the OS property, would not be able to join the device group after VS registration.		 ESX, ESXi
QCCR1D105257 "Network Name" and "VMware Guest OS" is not populated in the Virtual Machine Definition step after Modifying a virtual machine. Independent
QCCR1D108705 Need a better error message when Run Custom Extension is attempted on vCenter managed ESX/ESXi servers. Independent
QCCR1D109849 When you add vCenter whose hypervisors are already managed by SA, the job fails with "integrity constraint (TRUTH.DEVICES_VSWITCH_INTERFACES_FK) violated - parent key not found". Independent
QCCR1D109874 In the Server browser Properties view, the user name appears as Username=<empty> and Credential Status=unverified for the ESXi hypervisor. Attempts to set the credentials results in an error (java NullPointerException). VMware ESXi
QCCR1D109887 Snapshot views of hypervisors that are managed by Virtual Center (VC) are not supported. ESX, ESXi
QCCR1D110481 Starting a managed Hyper-V virtual machine is logged in the SA Web Client as "Start Zone". Microsoft Hyper-V
QCCR1D111307 The add ESXi operation suspends on RHAS3 and RHAS4 cores. VMware
QCCR1D111363 Modify VM fails when trying to modify/remove vlan adapter type VMXNET 2 or 3.  ESX, ESXi
QCCR1D111590 Incorrect history events are logged by failed, recurring, hypervisor scans. Independent
QCCR1D111691 The Virtualization panel displays a "java.lang.IndexOutOfBoundsException" and then the view panel goes blank. Independent
QCCR1D111775 Debug information is logged in the Web Services Data Access Engine (twist) stdout.log file. Vmware, Solaris
QCCR1D111780 Hypervisors are not loading. ESX
QCCR1D111847 A virtual machine is in a powered on state and you can add a disk but not change the size of the new disk or change the datastore after one is selected.  Independent
QCCR1D111922 The create virtual machine job on an Agent managed ESX 3.5 fails with the error message: "com.vmware.vim25.VirtualMachineConfigSpec". ESX, ESXi
QCCR1D111972 The create virtual machine action fails on a managed ESX hypervisor when the virtual machine's datastore name contains special characters, including blanks, in the controlling XML file. ESX 3, ESX 4
QCCR1D112176 The Help button on the Add Hypervisor Progress window does not open the add hypervisor online Help topic. Independent
QCCR1D112376 The Power On, Power Off, Reset, Suspend, Modify, and Remove actions fail on virtual machines managed by ESX 3.05. Independent
QCCR1D112417 Modify VMware VM - Adding multiple hard disks to different datastores results in all disks being added to a single datastore. ESX, ESXi
QCCR1D112431 Modify VMware virtual machine "Jobs and Sessions" displays "Power Status" as the virtual machine state.  Independent
QCCR1D112733 When creating a Hyper-V virtual machine, you cannot enter any RAM value because the value was restricted to 8 MB. Independent
QCCR1D113607 During a virtual machine modification, when adding VHD, the File Location does not work for input without an ending backslash (\). Independent
QCCR1D113659 Modify VM - Virtual Machine Definition - When you add a description that includes the equals (=) character, it fails and displays the following error: "ValueError: too many values to unpack". Windows 2008
QCCR1D113887 Create Virtual Machine job fails to boot the virtual machine into the server pool.  ESX, ESXi
QCCR1D113891 Cannot create and provision an ESX virtual machine guest.  ESX, ESXi
QCCR1D115353 Storage Panel page of the Storage Snapshot is not displayed when a hypervisor is managed through Virtual Center (VC) in the SA Client.  ESX, ESXi
QCCR1D118605

Cannot select Windows 2008 R2 as VMware Guest OS if you create a virtual machine on ESX Server and provision Windows 2008 R2.

 Windows

Web Services Data Access Engine

QCCR1D60634

In certain cases, for example, moving a twistOverrides.conf file from one core to another that has different encrypted key material, the operation fails and the twistOverrides.conf file is truncated.

Resolution: Changes to changes to the twistOverrides.conf file are now written to a temporary file and the original is only overwritten on successful completion of an operation.

 Independent
QCCR1D72100 If $JAVA_HOME is empty, SA will use the Java version installed in /etc/opt/ opsware/j2sdk14/j2sdk14 which typically contains the SA-supplied Java version. However, if you have installed a different Java version or have installed an application that overwrites the Java version in that directory, you could have incompatibility problems. Independent
QCCR1D119166 When you try to submit any new jobs, you might receive a RemoteException or CacheFullException message. Independent
QCCR1D119389 The Web Services Data Access Engine memory usage is not safely bounded, resulting in CacheFull exceptions and OutOfMemory errors. The engine should work within the memory it has been granted and it should block clients when memory resources are low. Independent
QCCR1D120354 The recalc Device calculates memberships for private dynamic device groups created by deleted users. Independent
QCCR1D122834 Include the Web Services Data Engine entity-bean cache monitoring tool in the SA product distribution. Independent
QCCR1D129505

Various activities fail when the Web Services Data Access Engine performs resource-intensive operations, such as audits involving a large number of devices.

 Independent
QCCR1D130079 Web Services Data Access Engine fails when it tries to load and process an excessively large XML results set. Core
QCCR1D130303 Red Hat Network (RHN) channel-based RPM remediation result set does not scale correctly. Core
QCCR1D131619

Exporting audit results with a python script fails due to an invalid value in the content length of the HTTP header.

Independent

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

Documentation Errata


This section describes documentation errata.

Guides

SA 9.0 Administration Guide

SA 9.0 Policy Setters Guide

SA 9.0 Simple/Advanced Installation Guide

Source Destination Open
Port (s)		 Note
Management Desktops Slice Component bundle hosts 80, 443, 8080 Required
Direct access to Oracle database (reports, troubleshooting, management) Model repository (truth) host 1521 Strongly recommended to allow Oracle management
Management Desktops Slice Component bundle hosts 1004, 1018, 1032, 2222 [Optional] Useful for troubleshooting; ports represent spin, way, twist, and ogsh (ssh).
SA Core (Management Gateway) SA Core (Management Gateway) 2001 Required
SA Core (Management Gateway) SA Core in a different Multimaster Mesh (management gateway) 22, 2003 [Optional] For scp (default word replication, can be forwarded over 2001 connection), backup for 2001 if it is busy.
Slice Component bundles SA Agents (in same network) 1002 Required (only for the Agent Gateway managing the Agent).
SA Core (Management Gateway) Satellite/Gateway 3001 Required
SA Core hosts Mail server 25 Required for email notifications
SA Core hosts LDAP server 636 Required for secure LDAP access; port can change if you use unsecure LDAP.
SA Agents SA Core servers and Satellites managing the agent 3001 Required
SA Satellite/Gateway SA Core 2001 Required
SA Satellite/Gateway Managed Agents 1002 Required
BSAe Core Mail Server 25 Required for email notifications
BSAe Core SA Core 1032 Required
BSAe Core BSAe database 1521 Required
BSAe Desktop SA Core 443 Required
BSAe Desktop BSAe Core 8080,8443, 14445 Required
Data Miner (SA Core) BSAe Core 8443, 8873 Required

 

SA 9.0 Single-Host Installation Guide

SA 9.0 User Guide: Application Automation

On page 463, Chapter 11: OS Provisioning, (section. "Network Booting a Linux or VMware ESX Server using PXE") and page 468 (section. "Booting a Red Hat Enterprise Linux Itanium 64-bit Server in a Non-DHCP Environment"), Figure 98:

The Linux Itanium 64-bit image boot screen has been enhanced in SA 9.05 and now looks similar to this:

HP IA64 Bootloader

Please choose a boot image :

   > linux            - Linux 3 Build Agent
   > linux-txt        - Linux 3 Build Agent for serial consoles.
   > linux            - Linux 5 Build Agent
   > linux-txt        - Linux 5 Build Agent for serial consoles.
   > winpe            - Windows Build Agent (WINPE IA64)
   > exit             - Exit
  
In this screen:

SA 9.0 User Guide: Server Automation

SA 9.01 User Guide: Server Automation

Storage Visibility and Automation Installation & Administration Guide

Storage Visibility and Automation User Guide

Online Help

Application Deployment Manager Context-Sensitive (F1) Help

In Application Deployment Manager, context-sensitive online Help is provided for numerous dialogs, including the Manage Applications and Manage Targets dialogs.

To view a context-sensitive help topic, click the question mark icon in the dialog. Note that the F1 key does not open online Help for the Application Deployment Manager.

To view the portion of the SA online Help that pertains to application deployment, select Help > Help in the Application Deployment Manager.

Refer to the HP Server Automation Application Deployment Manager User Guide for additional information.

Other Documents

Oracle Setup for the Model Repository Document

Support Matrix

Due to a documentation error, AIX 5.2 was previously listed as a supported platform for the SSI feature in the Support and Compatibility Matrix. The SSI feature is not compatible with AIX 5.2.

Back to the Table of Contents

----------------------------------------------------------------------------------------------------------------------------------------------------------

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

To access the Self-Solve knowledge base, visit the Self-Solve knowledge search home page.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

 

Back to the Table of Contents
----------------------------------------------------------------------------------------------------------------------------------------------------------

 

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices

© Copyright 2000-2011 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.
Intel® and Itanium® are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®‚ Windows® XP are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

Documentation Updates

To check for recent updates or to verify that you are using the most recent edition of a document, go to:
http://support.openview.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and sign in.
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service.
Contact your HP sales representative for details.

Back to the Table of Contents

Revised publication date: November 2011