Release Notes

HP Server Automation, Enterprise Edition


Software version: 10.01


Original Publication Date: October 18, 2013

Enterprise and Standard Editions

There are two editions of Server Automation:

For information about using SAVA and differences between the Standard Edition and the Enterprise Edition, see the SAVA at a Glance guide.

Up-To-Date Documentation

Get the most up-to-date version of the documentation on the HP Software Product Manuals portal. Additionally, all guides are cataloged for easy access in the SA 10 Documentation Library.

This site requires that you sign in with your HP Passport. If you do not have one, click the New users - please register link on the HP Passport login page to register.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. Note the Document Release Date on the title page of your guide and see the Documentation Change Notes on page 3 of most documents for a list of any revisions. The release-notes change table is at the bottom of this document.

Audience

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


 

Table of Contents

This document contains the following information:

What's New in This Release

Installation

Known Issues

Fixed Issues

Documentation Information

HP Software Support

Legal Notices

 


What's New In this Release

This section describes new functionality and other relevant release-specific information.

For information about what was new in previous releases, please see the corresponding release notes at:
http://support.openview.hp.com/selfsolve/manuals.

What's New for Supported Microsoft Windows Platforms

PowerShell v3 support was added for all supported versions of Microsoft Windows Platform.



What's New for Installation

Core and Satellite installation of patches has changed. See Core Patch Installation and Satellite Patch Installation.

Instructions for rolling back the patch have changed. See Rolling Back the Patch.

Reserved Ports

SA 10.01 requires that the following ports be open:

Note: In addition, other ports are required to be open for previous releases of SA. See the corresponding release notes at: http://support.openview.hp.com/selfsolve/manuals.

Upgrade

If your SA Core matches one of the SA Core configurations supported for customer upgrade and described in Chapter 2: SA Core Configurations in the SA Standard/Advanced Installation Guide, you can upgrade from a previous SA version to SA 10.01 yourself. However, if your core does not match any of these SA Core configurations, your first upgrade of an SA Core to SA 10.01 from a previous version must be performed by HP Professional Services or an HP certified consultant.

After the core has been upgraded to SA 10.0, HP supports customer-performed upgrades to SA 10.x or later as long as your core configuration is one of the supported configurations. All other core configurations will continue to require the services of HP Professional Services. If you are uncertain whether you can upgrade an existing SA Core yourself, contact HP Technical Support.

Warning: Job Loss During Upgrade and Rollback

SA 9.15, 9.16 and 10.01 provide an enhancement that improves performance and scalability for Linux remediation. Unintended deletion of certain jobs occurs when you upgrade to these versions (or rollback from these versions to certain previous versions) for jobs scheduled after the affected versions are installed.
The following types of jobs (both pending jobs and jobs that have already been run) are deleted if they are created after the affected version is installed:

The affected job information includes job state, job parameters, packages evaluated for the job, target servers, and values for subsequent phases, if only some of the phases were run (analyze, download, action). Server Automation stores this job information in the job history, and deletes it after 30 days by default.

To avoid losing your jobs and associated information, follow the instructions in the Server Automation Alert: Deploy the Remediation Job History Loss Fix SRVA 00176 at the following site: http://support.openview.hp.com/selfsolve/.


What's New for Qualified Managed Platform Support/OS Systems Support


SA Client Support for Windows Operating Systems

This section lists the operating-systems supported on the SA Client.

Support and Compatibility Information

For complete SA support and compatibility information, see the HP Server Automation Support and Compatibility Matrix for this release at: http://support.openview.hp.com/sc/support_matrices.jsp.

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 at the same link.

All SA and Storage guides are available at: http://support.openview.hp.com/selfsolve/manuals.

For more information about supported configurations, see SA 10.0 Standard/Advanced Installation Guide, chapter 2: “SA Core Configurations Supported For Customer Installation”.


What's New for Deprecated Agents and Features

This section lists deprecated platforms for this release.

When a platform/agent/feature is identified as deprecated for a release, it means that you (the SA customer) are considered 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.

Agent Upgrade Tool

The Agent Upgrade Tool that is run from the OPSH shell and allows upgrading the agents on managed servers was deprecated. As of SA 10.0, a replacement APX was introduced that has several improvements and can be run from the SA Client.

SA Agents

SA no longer supports SA Agents associated with SA 7.8x and earlier versions.

Pre-SA 10.0 agents are supported only in upgraded cores.

If you upgrade to SA 10.01, it is recommended that you migrate to the newest versions of the SA Agent on your managed platforms if you want to use the new SA 10.01 features.

API Methods

Since 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


What's New for Unsupported Platforms/Agents/Features


Unsupported Managed Platforms for SA 10.0

The following platforms are no longer supported as of SA 10.0:


Unsupported Features


Code Deployment and Rollback (CDR) and Configuration Tracking

Code Deployment and Rollback (CDR) was deprecated in the SA 7.80 release, and is no longer supported. The Application Deployment Manager replaces the CDR. See the SA User Guide: Application Deployment Manager for more information.

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


Virtualization Features

Legacy Job Types No Longer Supported New Replacement Job Types
Clone Virtual Machine (VMware) Clone Virtual Machine
Create Virtual Machine (Hyper-V)
Create Virtual Machine (VMware)
Create Virtual Machine
Delete Virtual Machine (Hyper-V)
Remove Virtual Machine
Delete Virtual Machine
Modify Virtual Machine
Modify Virtual Machine (Hyper-V)
Modify Virtual Machine

Note:  Any scheduled or blocked jobs of the legacy job types will be marked as Deleted during migration.

Unsupported Scripts

Start and Stop Scripts

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

start_opsware.sh
stop_opsware.sh

Starting In SA 9.0, you must use the unified start script:

/etc/init.d/opsware-sas

For Example:

/etc/init.d/Opsware-sas start
/etc/init.d/Opsware-sas stop

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

Deprecated Scripts

opsware_installer/patch*.sh Script

As of SA 10.01, direct invocation of the opsware_installer/patch*.sh script to install the patch has been deprecated. This script was replaced with the opsware_installer/hpsa_patch.sh script.

For more information on how to use the opsware_installer/patch*.sh script, see Core Patch Installation and Satellite Patch Installation.

Instructions for rolling back the patch have also changed. See Rolling Back the Patch.


What's New for Remediation Performance and Scalability

When you install this patch (SA 10.01) on your core system, the Remediation Performance and Scalability component is installed automatically on all your SA satellites. The component is enabled to run by default after installation.

This section describes how to enable and disable the Remediation Performance and Scalability component.

Disabling the Component On SA Satellites

To disable the Remediation Performance and Scalability component on SA Satellites:

  1. Log in to the satellite as root user.
  2. Enter the following two lines at the command line, pressing Enter after each:

    touch /var/opt/opsware/tsunami/tsunami.disabled
    /etc/init.d/opsware-sas stop tsunami

Note: After you disable the component on the satellites, you cannot restart it unless you perform the steps in Enabling the Component on SA Satellites. If you do try to restart the Remediation Performance Scalability component, you will see the following error message:

>>> Starting tsunami ...
Tsunami has been disabled, will NOT start tsunami
Successfully performed "start" operation on Opsware SAS components.

Enabling the Component On SA Satellites

To re-enable and restart the Remediation Performance and Scalability component on SA Satellites:

  1. Log in to the satellite as root user.
  2. Enter the following two lines at the command line, pressing Enter after each:
    rm –f  /var/opt/opsware/tsunami/tsunami.disabled
    /etc/init.d/opsware-sas start tsunami

What's New for OO-SA Integration

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


What's New for Oracle Database and Model Repository

As of SA 10.0, the schema and index statistics collection for SA database users AAA, TRUTH, and so on have been moved from dba_jobs to Oracle's Automatic Optimizer Statistics Collection. Starting with SA 10 you will no longer see these jobs in dba_jobs.

Starting with Oracle 10g, the DBA_JOB package was superseded by the improved Oracle Scheduler (dba_scheduler) package. Although Oracle still supports the DBA_JOB package for backward compatibility, Oracle will make no further enhancements to the package. Since the DBA_SCHEDULER provides better functionality, all the SA jobs that used the DBA_JOB package have been redesigned in this SA release to use the DBA_SCHEDULER package. The affected jobs can be found in the dba_scheduler_jobs table. These changes are only relevant to new SA 10.0 Cores and cores upgraded to SA 10.0.

To view the jobs and changes made, you can run the following from SQL*Plus:

# Su - oracle
# Sqlplus "/ as sysdba"
SQL>set line 200
SQL>col owner format a14
SQL>col job_action format a50
SQL>col job_name format a50
SQL>select job_name, owner, job_action from dba_scheduler_jobs where owner in
('OPSWARE_ADMIN', 'LCREP', 'GCADMIN');

Oracle RAC

This release supports Oracle 11.2.0.3, but it is recommended that you use Oracle 11.2.0.3.7 or above for this release.

For more information on Oracle RAC, see the SA installation guides.


What's New for OS Provisioning


What's New for Build-Plan OGFS Script Execution

In previous SA versions, if you created OGFS scripts and added them to your build plans, the scripts were executed in the file system in the following directory:

/opsw/.Server.ID/<mid>/files/<user>

Now, the scripts are executed in this new location:

/opsw/.Server.ID/<mid>

As a result of this change, you must add the following line to your build-plan scripts to avoid compatibility issues with user scripts:

cd files/root (Linux)

cd files/Administrator ( Windows)

 

OS Build-Plan Support for VMware ESXi5 and ESXi5.1

SA briefly stops the VMware ESXi firewall in order to communicate the VM's IP Address, so that it can be managed by the SA core. SA restarts the firewall immediately afterwards.

If you do not want SA to stop and start the firewall, use static OS Provisioning instead.

Enhanced HP ProLiant Support

ProLiant support includes:

For more information, see the SA README.html, SA UG: OS Provisioning guide, and the SA online help.

Support for OS Build Plans

HP ProLiant Gen8 models have two embedded service operating systems available: Linux and Windows Preinstallation Environment (Windows PE). SA can use either the Integrated Lights-Out (iLO) functionality of these embedded systems, or Preboot Execution Environment (PXE) booting.

To use the embedded systems' iLO functionality, you must add your server as an iLO device to the list of unprovisioned servers.

There are two ways to do this:

In both these cases, you will need to manually provide iLO credentials and the corresponding SA realm (which is related to the SA Satellite or core available in the target network). This information defines the SA infrastructure to be contacted after the embedded service operating system is booted. When you use PXE booting, this information is provided by the PXE server automatically.

For more information on how to add your server, see" Installing (Provisioning) an Operating System" in the UG: OS Provisioning.

Operating System Build-Plan Updates

New Features

The following new features have been added to build plans:

Enhanced Steps

The following 3 steps have been enhanced, or added, to build plans for HP ProLiant Gen8 support.

Virtual Installation Device (VID) handling

HP ProLiant Gen8 devices support special Virtual Installation Devices (VIDs).

SA handles VIDs as follows:

For more information on this topic and for specific use case, see "Prepare Disks on HP ProLiant Gen8" in the SA OS Provisioning README.

Running OS Build Plans on Servers

Build plans can now be run on servers that are in the pre-unprovisioned lifecycle.

SLES 11 SP1 kISO Handling

If you are using SuSE Linux Enterprise Server (SLES) 11 SP1 and above, you must do the following to support the SuSE kernel & driver update method using kISO:

  1. Download the kISO & mount the ISO file for access.
  2. Create (or reuse) a SLES distribution repository in a directory (for example: /repositories/SLES-11-SP1-x86_64).
  3. Create a new directory called addon (the directory name does not have to be case sensitive, you can also use AddOn or ADDON) under your new repository directory (for example: /repositories/SLES-11-SP1-x86_64/addon).
  4. Copy the kISO contents to the addon directory.
  5. Replace the original installation kernel and initrd files with the kISO files found in the addon directory.
  6. Copy the contents of the addon/boot/x86_64/loader/initrd directory to the following directory: boot/x86_64/loader/initrd.
  7. Copy the contents of the addon/boot/x86_64/loader/linux directory to the following directory: boot/x86_64/loader/linux.

Note: If you experience driver problems with SLES 11 SP1 and kISO on HP ProLiant Gen8 target machines, see the following technical support documents:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03237879
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03237878

For more information on kISO handling, see the kISO media documentation and the OS Provisioning README.

OS Build-Plan Custom Attributes

Custom attributes set on the build plan will now be resolved and used in parameters and scripts during the execution of the build plan. If a custom attribute with the same name exist anywhere else on or in the servers’ hierarchy, its value will take precedence over the value set on the build plan. This is the priority order from highest to lowest:

  1. server
  2. device group
  3. customer
  4. realm
  5. facility
  6. OS
  7. software policy
  8. (new) OS build plan

Driver Update for HP ProLiant G6/G7 Servers

SA service operating-system drivers have been updated with the latest HP ProLiant SP drivers: SPP 2012.02 b51.

Multipath SAN Support for OS Provisioning

As of this release, SA provides multipath SAN support for the topics listed in this section.

OS Sequences

Red Hat 6 automatically identifies multipathing and enables kernel modules, but Red Hat 5 does not.

For Red Hat 5, before you run the Red Hat Enterprise Linux (REL) 5 OS Sequence, use the following steps to pass mpath' as a kernel argument for the server:

  1. Define a custom attribute kernel_arguments for the server, and set its value to mpath.
  2. Create the OS Installation Profile.
  3. Add a custom attribute to the Installation profile, and set its value to mpath.
  4. Set the value of the installation profile to mpath.

If you are performing multipath installation, it is also recommended that you add mpath as the kernel argument in the kickstart Red Hat 5 file. You can do this by creating a copy of Configure Default Red Hat 5 ks.cfg and modifying the file for use in your OS build plan.

SUSE Linux Enterprise Server 11

SUSE Linux Enterprise Server 11 does not identify multipathing by default. Use the procedures in this section to install SUSE Linux Enterprise Server on multipath LUNs.

Windows 2008/ Windows 2008 R2

Windows supports installations in multipath environments. Install multipath Device Specific Modules (DSMs) to further improve the capabilities of the target server. Import these DSMs into the SA Software Repository and install them using software policies attached to OS sequences.

You can modify the SAN Policy for the Windows Service OS (Winpe32, winpe64, winpe32-ogfs, winpe64-ogfs) shipped with SA. For more information about available options, see: http://technet.microsoft.com/en-us/library/cc749466(v=ws.10).aspx.

The default SAN Policy registry value in the SA-provided Windows pre-installation environment (WinPE) boot image is 1.

VMWare ESX/ESXi

VMWare ESX and ESXi support multipathing - no additional steps are required.

Use the Inject Multipath AutoYaST step

You must add the Inject Multipath AutoYaST Settings step to the OS build plan.

Perform the following tasks:

  1. Create a new OS build plan by copying the default SUSE Linux Enterprise Server 11 Install Build Plan from the SA Client library.
  2. Add the Inject Multipath AutoYaST Settings step after the Install And Configure SUSE Build Image step.
  3. Add the Embed Files Initrd step after the Inject Multipath AutoYaST Settings step with the following parameters:

    -s /tmp/user.autoinst.xml:/

The drive injections in the AutoYaST will be performed based on the criterion defined in the OS sequences (see Partitioning Section in AutoYaST).

Server Location Display

The Server Location node shows the server’s physical location. The General category in the node displays the following information:

Note: The server location section only displays information about the HP ProLiant BL servers.

Accessing Partitions in Linux Service OS ( maintenance mode )

You can already access your local-system partitions at: /mnt/<<device name>>. As an enhancement of SA 10.0, you will also be able to access your partitions in /mnt/by-uuid and /mnt/by-label to ease the identification of the partitions.


What's New for Solaris 11


New APIs

To support Solaris 11, the following classes were added to the UAPI:

Solaris 11 Memory Requirements

Solaris 11 servers must have more than 1 Gigabyte memory in order to enter the SA Managed Server Pool.

Solaris 11 Patching Support

Oracle Solaris 11 uses IPS packages to deliver software and software updates. IPS (Image Packaging System) is a network-based package management system that is used for the entire software lifecycle, including package installation, upgrade and removal.

Server Automation's Solaris 11 platform support for server patching allows you to update your managed servers to the latest versions of existing software without installing new software. This is a powerful way to keep your system up to date in an environment that no longer supports explicit patch units.

Solaris 11 patching support leverages the existing Solaris patching functionality, with a few differences to adapt to the new Solaris IPS package delivery structure. Additionally, there are setup requirements for setting up the initial IPS Package database.

Note: The SA 9.13 Solaris 11 Patching Whitepaper applies to all SA versions, starting with SA 9.13, and provides detailed instructions on setting up and maintaining the IPS Package database. This document also describes the Solaris 11 patch policy and remediation differences. This whitepaper is available via HP's Software Support Online at http://support.openview.hp.com/selfsolve/manuals.

Using Server Modules (SMOs) with Solaris 11

Solaris 11 introduces Role-based Access Control (RBAC), which affects the functionality of SA Server Modules (SMOs). SMOs rely on the root user to get information from the managed servers. In previous versions of Solaris, the root account is created as a user by default, with the option to have it as a role. In Solaris 11, the root account is created as a role by default; not as a user.

In order to enable the SMO functionality, the system administrator must modify the root account (root) to make it a user with regular login capability. The best method for doing this is to run an ad hoc script on the managed server.

To enable root for regular login capability:

  1. Navigate to Devices > Servers > All Managed Servers.
  2. Right-click on the target server and select Run Script > Select Script… and choose Define Ad hoc Script.
  3. In the Script Contents, enter the line ‘rolemod -K type=normal root’ and click Next.
  4. Choose Runtime User: root and click Start Job.

    After the job completes the user will be able to run the SMOs on the selected servers.

Note: To change the root account to a role again, complete the same procedure but enter ‘usermod -K type=role root’ in the Script Contents.


What's New for Storage Essentials


Migration Instructions


Migrating from SA 7.8 to SA 10.01
  1. Upgrade to 9.10.
  2. Upgrade to 10.01.

Migrating from SA 9.0x to SA 10.01

  1. Rollback to 9.0  .
  2. Upgrade to 10.01.

Migrating from SA 9.1x to SA 10.01

  1. Roll back to 9.10.
  2. Upgrade to 10.01.

Note: If the upgrade fails with an Oracle missing permissions error, perform the following procedure:

  1. Connect to the Oracle database.
  2. Issue the following commands:
    1. Su – oracle
    2. Sqlplus / (as sysdba)
    3. Sqlplus>grant create job to opsware_admin with admin option.

What’s New for Virtualization Management

See the Unsupported Features section of these release notes for unsupported virtualization features.



Patch Installation

There is a new patch-installation procedure.

General Installation Information


Core Patch Installation

This section discusses how to install this patch on the core SA server.

To install the patch on the core SA server:

  1. On the core host, enter the following command to run the patch script:
    <distro>/opsware_installer/hpsa_patch.sh

    Where <distro> is the full path to the DVD or mounted media. For example:

    /<distribution mountpoint>/<prefix>-patch/disk001

    After you enter the command, you see messages displayed on the screen similar to the following:

    patch will be performed on the following identified core host(s).
    If there is any inconsistency then try again with the correct Core Definition File (CDF).

    16.77.1.60  (gateway_master, truth_mm_overlay)
    seatrout.rose.hp.com  (word_store, osprov_media, slice, osprov_boot_slice)

  2. Press Enter at the following prompt:

    Do you want to continue (Y/N) [Y]:Y

  3. Enter the host password at the following prompt:

    <host_name> password []:

    The system validates the password.

Entering the hpsa_patch.sh  command and the host password completes the patch installation on the SA core.

Note: The opsware_installer/hpsa_patch.sh script can be invoked on an infrastructure SA host without providing a Core Definition File (CDF). When invoked in this manner, the script automatically reads CDF information from the default location. Alternatively, the script reads the CDF location from /var/opt/opsware/install_opsware/cdf/cdf.xml when you use the script with the following argument:
-c cdf.xml


Satellite Patch Installation

This section discusses how to install this patch on a satellite SA server.

To install the patch on a satellite server:

  1. On the satellite host, enter the following command to run the patch script:
    <distro>/opsware_installer/hpsa_patch_satellite.sh

    Where <distro> is the full path to the DVD or mounted media. For example:

    /<distribution mountpoint>/<prefix>-patch/disk001

    After you enter the command, you see messages displayed on the screen similar to the following:
    patch_satellite will be performed on the following identified core host(s).
    If there is any inconsistency then try again with the correct CDF.
    16.77.1.187  (wordcache)
    16.77.1.188  (osprov_boot_sat)
    brook.rose.hp.com  (osprov_media_sat)

  2. Press Enter at the following prompt:

    Do you want to continue (Y/N) [Y]:Y

  3. Enter the host password at the following prompt:

    Parameter 1 of 2
    <host_IP_address> password []:

    The system validates the password.

  4. Enter the satellite password at the following prompt:

    Parameter 2 of 2
    <satellite_name> password []:

Entering the hpsa_patch_satellite.sh  command and password completes the patch installation on the satellites.


Rolling Back the Patch

To roll back the SA 10.01 patch on the host to SA 10.0, enter the following command:
<distro>/opsware_installer/hpsa_patch.sh  --rollback

To roll back the SA 10.01 patch on the satellite to SA 10.0, enter the following command:
<distro>/opsware_installer/hpsa_patch_satellite.sh  --rollback

Warning: Job Loss During Upgrade and Rollback

SA 9.15, 9.16 and 10.01 provide an enhancement that improves performance and scalability for Linux remediation. Unintended deletion of certain jobs occurs when you upgrade to these versions (or rollback from these versions to certain previous versions) for jobs scheduled after the affected versions are installed.
The following types of jobs (both pending jobs and jobs that have already been run) are deleted if they are created after the affected version is installed:

The affected job information includes job state, job parameters, packages evaluated for the job, target servers, and values for subsequent phases, if only some of the phases were run (analyze, download, action). Server Automation stores this job information in the job history, and deletes it after 30 days by default.

To avoid losing your jobs and associated information, follow the instructions in the white paper: Deploy the Remediation Job History Loss Fix SRVA 00176 at the following site: http://support.openview.hp.com/selfsolve/.

 



Migrating from SA 7.8, SA 9.0x, and SA 9.1x to SA 10.01


Migrating Order

When migrating from SA 7.8 to SA 10.01:

  1. Rollback your SA Core to SA 7.8.
  2. Upgrade the SA Core to SA 10.0.
  3. Upgrade the SA Core to SA 10.01.

When migrating from SA 9.0x to SA 10.01:

  1. Rollback your SA Core to 9.0.
  2. Upgrade the SA Core to SA 10.0.
  3. Upgrade the SA Core to SA 10.01.

When migrating from SA 9.1x to SA 10.01:

  1. Rollback your SA Core to SA 9.1.
  2. Upgrade the SA Core to SA 10.0.
  3. Upgrade the SA Core to SA 10.01.

Adobe Flash Player


HP BSA Launcher Issues

Certain SA Client features (such as Run OS Build Plan or HP UX Provisioning) require the Adobe Flash Player. If you try to run these features, and you have not yet installed Adobe Flash Player, you will get an error.

To make sure Adobe Flash Player functions correctly and to avoid the error message, you should:

  1. Stop any instances of the SA Client.
  2. Using Internet Explorer, access the following site: http://www.adobe.com/software/flash/about/
  3. Make sure that the latest version of Adobe Flash Player is installed in Internet Explorer.
  4. Restart the SA Client and run the features normally.

The error message should not display.



Post-Installation Tasks

This section lists the tasks that should be performed after you install this patch. Some tasks might not be appropriate for your situation.

Installing Red Hat EL 5.9

If SA 10.01 is installed on Red Hat EL 5.9, sporadic org.omg.CORBA.COMM_FAILURE exceptions will be displayed in the SA Client console.

To work around this issue, after install or upgrade:

  1. In order for the kernel parameters to persist across restarts, set the sysctl parameters in the /etc/sysctl.conf file:
    net.ipv4.tcp_tw_recycle=1
    net.ipv4.tcp_tw_reuse=1
  2. Load the sysctl.conf settings you edited in Step 1: 
    # sysctl -p

  3. Set the property to not use the socket option: SO_REUSEADDR on all gateways:
    # edit /etc/opt/opsware/opswgw-agw*/opswgw.custom
    # edit /etc/opt/opsware/opswgw-cgw*/opswgw.custom
    # edit /etc/opt/opsware/opswgw-mgw*/opswgw.custom

    Directive:
    opswgw.SoReuseAddr=false

  4. Restart all gateways using the following command:
    service opsware-sas restart

Redhat has a description of this issue on their website: https://access.redhat.com/site/solutions/357683


Windows Server OCLI Installation

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


Installing Slices

If you install additional Slice Component bundle instances after patching the SA Core, wayscript versions are set to version 10.0 rather than to the patch version. Use the following procedure to remedy the situation:

  1. Identify the SA core server by checking the value field of the custom attribute CORD_OPSWwayscripts. To do so, log in to the SA Client as administrator (opsware admin user) and navigate to Administration > Customers. Select the Opsware Customer and view the Custom Attributes.
  2. Log in to the SA Core server you identified in step 1 and execute the following two commands:

    Command #1:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts

    Command #2:
    ./post_after_startup.sh
  3. Apply any required hotfixes to the wayscripts.

Upgrades

 

Customized Settings

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

Upgrading SA Agents

After you upgrade to this patch, you should also upgrade to the 10.01 SA Agents on each Managed Server in the facility. If you do not upgrade your agents, the new functionality will not be available.


Post-Upgrade Tasks


Patch De-duplication Steps for Windows Patching

Duplicate patches can be inadvertently created in the SA database if you import the Microsoft Patch Supplement (MPS) and then run the SA Patch Import process using the Microsoft Offline Patch Catalog (wsusscn2.cab). These duplicates can cause conflicts during remediation and compliance checks. SA provides a Windows patch de-duplication process that enables you to eliminate these duplicates and resolve this issue.

IMPORTANT
: When to perform the de-duplication process:
The Windows patch de-duplication process is only required for SA upgrades, and is only required to be performed once:

How do I know if I have duplicates?
Starting in 9.14, the patch database has a new field, “Last Import Summary, which reports if any duplicates were found in your database. In the SA Client, navigate to Administration > Patch Settings > Patch Database to view this field. If it displays a warning message after performing a patch import, then there are duplicates in your database. If duplicates are found, these de-duplication steps are strongly recommended.

Resolving Duplicates
To resolve this, a one-time de-duplication procedure is available that enables you to remove the duplicates and eliminate the source of these conflicts to prevent future duplication. 
Step-by-step instructions are provided in the whitepaper, Resolving Conflicts between SA Patching and the MS Patch Supplement, which is available on the HP Software Support Online site under the 9.15 Server Automation release.

IMPORTANT
: The de-duplication procedure varies based on your version of SA. For this reason, there will be multiple versions of this whitepaper, each providing release-specific instructions. Be sure to use the version of the whitepaper recommended for this release.

To find the whitepaper:

  1. Go to HP Software Support Online: http://www.hp.com/go/hpsoftwaresupport
  2. Click the Self-solve tab.
  3. Log in using your HP Passport credentials.
  4. Complete the search criteria:
    1. Exact Phrase: HPLN MS Patch Supplement
    2. Product:  Server Automation
    3. Version: 9.15
    4. Document types: Manuals and White Papers
    5. Sort by: Relevance
  5. Click Search.
  6. Scroll down to see the results.
  7. Find filename: SA_9.15_Windows_Patching_n_Patch_Supplement_wp.pdf

You can also do the same search directly from the SSO Product Manuals site: http://support.openview.hp.com/selfsolve/manuals

Back to the Table of Contents



Known Issues

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

Known Issues

QCCR1D Symptom/Description Platform Module Workaround

Administration User Interface

QCCR1D147462 Web Services Data Access Engine (Twist) stops functioning when the WebLogic Server Administration Console is accessed. As a consequence, the WebLogic Server Administration Console is disabled in SA 10.01, by default.

 

Independent Administration UI To enable WebLogic Server Administration Console:

  1. Edit /opt/opsware/twist/twist.sh:
    1. Remove -XX:+UseCompressedOops.
    2. Replace:OPTION_COMPRESSEDOOPS="-XX:+UseCompressedOops" with OPTION_COMPRESSEDOOPS="".
  2. Edit /var/opt/opsware/twist/config/config.xml and remove "<console-enabled>false</console-enabled>".
  3. Save these 2 files.
  4. Restart the Web Services Data Access Engine (Twist) and access the console.

If, after you have completed the procedure described above, you want to use the Web Services Data Access Engine instead of the WebLogic Server Administration Console:

  1. Roll back the changes in #1 and #2 above.
  2. Restart the Web Services Data Access Engine .
QCCR1D157288 The My Profile window throws an authorization error when the user is part of Customer Group Admin.

Windows Administration UI "Customer Admin" users are not supported in the SA Client for SA 9.1x releases. Update your user profile in the SA Web Client instead.
QCCR1D166272 You cannot launch the SA Client after upgrading your core from an earlier version of SA to SA 10.01, and you receive a Launch File Error. Independent Administration UI

Follow these steps:

  1. Uninstall the old launcher.
  2. Download the new launcher by doing one of the following:
    1. Accessing the login page and downloading the new launcher.
    2. Logging-in to the core and, from the right panel in the home page, download the installer.
  3. Install the new launcher.

All the previous settings are retained and it should be able to launch without any issues.

Agent

QCCR1D91352 Agent deployment times are increased considerably (sometimes up to 30 minutes) if you try to deploy to a host that does not have the uudecode program installed.

In the staging phase of the Agent deployment process, the transmission of the binaries to UNIX/Linux hosts is done over a character stream. The binary files are encoded prior to the transmission and decoded once uploaded to the remote host (using the uudecode program). If uudecode program is not present on the remote host, ADT uses an inline implementation that is very slow.

Unix, Linux Agent Deployment Make sure that the uudecode program is installed on the host to be managed.
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.
QCCR1D137345/137348

Your Solaris satellites and managed servers cannot be accessed with OGFS, because your PAM library for Secure Shell (SSH) is incompatible with the SSH daemon that SA uses for OGFS.

Solaris Agent

To resolve the issue, add ptymonitor.nopam:1 to the agent.args file on Solaris. This will bypass the PAM-based authentication.

Caution: Contact HP Support for more information before you make this change.

QCCR1D140236

SA Agent scan for installed software fails.

RHEL 5 x86 - 64 Agent Either rename the createrepo folder or add an RpmQueryCli: rpm line to the agent.args file that will instruct the SA Agent use the rpm command when searching for installed packages.
QCCR1D152367 Agent deployment is not allowed to Windows 2012 hosts with the firewall enabled and no firewall exception defined for port 139. Windows 2012 Agent Deployment/Upgrade

 

Disable the Windows firewall or add a firewall exception for port 139 (the ‘File and Printers Sharing’ exception template can be used).
QCCR1D156515 You cannot use pre-9.15 SA Agents to register new servers, you must use 9.15 SA Agents.

Independent Agent Install 9.15 SA Agents and use them to register the server.
QCCR1D156924/167887*** Software policy remediation of multiple packages with reboot option fails at install stage with batchbot error:

The operation to install or uninstall software failed.
Execution error: Traceback (most recent call last):
File "./base/wayfuncs.py", line 136, in evaluator
File " ", line 8250, in ?
File " ", line 8242, in main
File " ", line 7929, in action
File " ", line 7296, in actionImpl
File " ", line 6418, in processPreInstall
File " ", line 6427, in processBulkScripts
File " ", line 6434, in processPreInstallUnit
File " ", line 6499, in processScript
File "./batchbot.py", line 1860, in runSyncShellScript
File "./batchbot.py", line 1609, in get_batchbot
TypeError: unsubscriptable object

Independent Agent Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue.
QCCR1D168321*** Fujitsu hardware running on Solaris reports a partial serial number if the serial number is enclosed in single quotes. Solaris Agent Contact HP Support for information on a hot fix that addresses this issue.

Application Configuration

QCCR1D142320 Server Instance name is not automatically renamed at migration time. Windows

Software Management Do not use the same name for appconfigs and templates before upgrading from 7.8x to 9.15.

APX

QCCR1D116476 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 millisecond.

  3. Restart the Core.
QCCR1D160543 HPLN APX content developed for 'platform_linux' stream fails on content reload if managed platform content is already imported

.
Independent APX Tool None

Audit and Compliance

QCCR1D160469 As of SA 9.15, the following audit and snapshot fields for audit policy .nt rule Assembly Cache type have been removed or renamed:

  • Removed: Codebase and fData.
  • Renamed: fName to fileName, and languageid to languageID.
Independent Audit and Compliance Update any audit or snapshot with a rule that depends on any of these fields:

  • Removed fields: Codebase and fData.
  • Renamed fields: fName to fileName, and languageid to languageID.
QCCR1D168415 Audit Policy Compliance Checks Rule: "Reset Account Lockout Counter After" has a value limitation for remediation. This value must be less than or equal to lockout duration to 1800.

Request: Reset this value to 99999.
Independent Audit and Compliance None.

Audit and Remediation

QCCR1D81308 An erroneous status is displayed when remediation of registry and COM+ objects fails.
Windows Audit and Remediation - Backend None
QCCR1D147020/147816 Communication with an Agent timed out with a timeout type of: MAXIMUM.

Independent Audit and Remediation - Backend Use the following steps to change the timeout value in the GUI:

  1. In the SA Client, go to Administration > System Configuration
    SA > Command Engine > way.ssct_*timeout
    .
  2. Change the proxy remediate snapshot and snapshotcompliance timeouts from 1800 to 5400 (in seconds). These timeouts apply for all AnR jobs.
  3. Change the timeout value in the spoke.conf file:
  • Change the value for the spoke.handler.cmdoutput.timeout parameter to 5400. This value applies per check per target for pluggable and custom script checks.
  • Change the value for the spoke.handler.cmdoutput.timeout_atcore parameter to 5400. This value applies to all of the checks per target for pluggable and custom script checks.

Note: Changes to SA Core configuration parameter values, as listed in this Release Notes document, are verified by HP and you can safely apply them as directed. However, exercise caution when modifying other default SA Core configuration parameter values as modifications can have a negative effect on core functionality and performance.

QCCR1D151552 If you cancel a running audit job, and a target server shows a "SKIPPED" job status in the audit results, until an audit has successfully run, the server's compliance view shows the following incorrect status for the policy:

Policy has changed since the last scan”.

Independent Audit and Remediation Rerun the audit job.
QCCR1D161054 If you set an audit schedule in previous releases (pre-SA 10.0), and you used System time zones (such as SystemV/PST8 or System V/PST8PDT), you will receive a com.opsware.job.IllegalScheduleException error.

Independent Audit and Remediation Reset the audit schedule to use supported time zones.
QCCR1D162962 When you export audit results to XML, the results will not be correctly displayed if they include text that has an accented character. The following error appears in the results:

XML page cannot be displayed. Invalid character was found in text content.

Independent Audit and Remediation None
QCCR1D165732 Running a snapshot-based audit with multiple Perform Inventory rules will result in the following RuntimeException error:

Multiple Inventory checks are not supported for snapshot-based audit. Optionally, run the corresponding rule types with (*) option.

Independent Audit and Remediation Run the snapshot-based audit for corresponding rule types with the (*) option instead of the Perform Inventory option enabled.

BSA Essentials Dataminer

QCCR1D112784 In multimaster environments, Application Deployment data mismatches between SA and BSA Essention can occur 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

Data Access Engine

QCCR1D111804 Reloading the cache on 10 clients simultaneously makes the Data Access Engine (Twist) malfunction, and blocks access to the core server. Other users are unable to log in to the core.

The following error is displayed:

>>>>>>>>WebStartConsoleError<<<<<<<<<<<<<<
Java Web Start 1.4.2_15 Console, started Thu May 06 15:48:55 PDT 2010 Java 2 Runtime Environment: Version 1.6.0_18 by Sun Microsystems Inc.
Logging to file: C:\Documents and Settings\buslovic\Application Data\HP BSA\Cache\deployment\log\javaws\javaws1476906802910963403.log
FINE accepting connections on port 1098
FINE Protocol handlers: com.sun.javaws.net.protocol
FINE Connecting to Twist: https, 192.168.181.131, 443
May 6, 2010 3:49:04 PM com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl <init>
WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_SSL_WLS; hostname: 192.168.181.131; port: 443"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(Unknown Source)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(Unknown Source)
...
weblogic.corba.client.http.TunneledSSLORBSocketFactory.createSocket(TunneledSSLORBSocketFactory.java:59)
... 32 more


Independent Data Access Engine None

Database Scanner for Oracle

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
QCCR1D133226 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" will fail and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database.

The following error might be displayed under these circumstances:
"PLS-00905: object SYS.DBMS_NETWORK_ACL_ADMIN is invalid". 

Independent Database Scanner for Oracle Before executing the SA DB Scanner "pamuserprivilege.sql" 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.

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;

QCCR1D133266 DB Scanner run "pamuserprivilege.sql" and DB Scanner snapshots fail on Oracle 11G databases with the following error:

object SYS.DBMS_NETWORK_ACL_ADMIN is invalid

Under these circumstances, you cannot discover and view  Oracle databases.

Linux, Windows Database Scanner for Oracle Use the following steps to run DBScanner snapshot on managed servers:

  1. Run the Storex snapshot on the target managed server, where you configured the database instance.
  2. Navigate to Administration Panel > Storage Scanner > Oracle DBScanner > Add login credentials.
  3. Add the targeted managed server name mentioned in Step 1 and provide the database instance name (SID).
  1. Create and run the DBScannersSnapshot - the run will fail at this time, but it will import the SQL scripts pamuserprivelege.sql, configureXMLDB.sql and configureXMLDB_Windows.sql.
  2. Connect to the target managed server and execute the following commands.

    Linux:  cd /opt/opsware/dbscanner.oracle/lib/   
    Windows: cd C:\Program Files\Opsware\dbscanner.oracle\lib

  3. (Linux) Change the script permissions:

    chmod 777 * 
    su – oracle

  4. Connect to sqlplus and run the following commands and scripts:

    sqlplus /nolog
    SQL> connect <sys_user>/<password> as sysdba
    SQL>@configureXMLDB.sql (For Linux)
    SQL>@configureXMLDB_Windows.sql (For Windows)
    SQL>@pamuserprivilege.sql

QCCR1D156262 Snapshots for SMO fail while parsing the configuration file found on the server.

Independent Database Scanner for Oracle To enable correct snapshot functionality, use one of the following two procedures:

Procedure One: Complete Database Installation:

  1. Run the Database Scanner snapshot on the managed server to be discovered:

    For Linux, issue the following command:
    /opt/Opsware/dbscanner.oracle/lib

    For Windows, run the following script:
    C:\Program Files\Opsware\dbscanner.oracle\lib

    This action will fail the first time you try it, but it is a mandatory step because it enables the server to copy necessary SQL files to the target server.

  2. For Customized installations, run the following scripts:
    • configureXMLDB.sql
    • pamuserprivilege.sql

    These scripts create the login credentials to discover the database metadata.

  3. Rerun the snapshot.

Procedure 2: Complete Install:

  1. Run the Database Scanner snapshot on the managed server to be discovered:

    For Linux, issue the following command:
    /opt/Opsware/dbscanner.oracle/lib

    For Windows, run the following script:
    C:\Program Files\Opsware\dbscanner.oracle\lib

    This action will fail the first time you try it, but it is a mandatory step because it enables the server to copy necessary SQL files to the target server.

  2. Run the pamuserprivilege.sql script. This scrip creates the login credentials to discover the database metadata.
  3. Rerun the snapshot.

Database and Middleware Automation (DMA)

QCCR1D133378 Workflow cancellation indicates success in the DMA Console, but workflow runs to completion on SA managed server. Independent DMA Use the appropriate process manager for the managed server's Operating System (for example, kill for UNIX and Task Manager for Windows) to manually terminate the process. 
QCCR1D146469 If you run the da_baseline.sh -erase command manually in order to delete all of your Database and Middleware Automation data and reload the default data, the Discovery solution pack is not reloaded. Independent DMA Follow these steps to import the Discovery solution pack:

  1. Copy the following file from the SA Core server to the system where you will access the Database and Middleware Automation user interface (UI): /opt/opsware/da/webapps/dma/discovery/Discovery.zip
  2. On that system, open the Database and Middleware Automation UI in a browser:
    http://SACoreServer/dma/login.
  3. Log in using your SA user name and password.
    At least one of your roles must include the Manage Database & Middleware Automation SA action permission.
  4. On the Solutions ® Installed page, browse to the Discovery.zip file that you copied in step 1.
  5. Click Import.

Gateways (Bandwidth Configuration Tool)

QCCR1D147794 Provide warning for bandwidth throttle behavior in 9.06 -> 9.0 -> SA 10.x upgrade path.

Independent Gateways (Bandwidth Configuration Tool) During the 9.06 to 9.0 rollback, changes made in 9.06 to the Bandwidth Configuration Management Tool (including properties files changes and to the default BWT.conf file) are deleted (undone).
When you upgrade the core to SA 10.01, perform the following task to restore your configuration:

From a Slice Component bundle host (or from a Satellite host), run the following command to push the configuration file:

/opt/opsware/opswgw/bin/gwctl -f <path_of_your_config_file>

 

After you upgrade your core to SA 10.01, the SA 9.0 satellite is unreachable. Independent Gateway For 9.0 Satellites to work with SA 10.01, an Egress filter must be modified in the Gateway.

For example, for a 9.0 Satellite that connects to TOMATOSAT1 Core:

  1. Change the Gateway configuration as follows:

    Original Gateway Filter:
    opswgw.EgressFilter=tcp:*:1002:*:TOMATOSAT1
    Change to :
    opswgw.EgressFilter=tcp:*:1002:*:*

  2. Restart the satellite gateway.
  3. **Important ** After upgrading the satellite to SA 10.01 the Gateway filter must be restored to the original filter. In this case, restore it back to:

    opswgw.EgressFilter=tcp:*:1002:*:TOMATOSAT1

QCCR1D183895

If you only upgrade your SA Core from 9.1x to 10.0, then upgrade to 10.01, but do not upgrade your SA satellites in the same maintenance window, the satellite facility and its managed subsystem become unreachable.

Linux Gateway Upgrade your satellites at the same time as you upgrade your SA core.

Global File System

QCCR1D167608*** Failures running OGSH commands in SA from OO. Independent OGFS Contact HP Support for information on a hot fix that addresses this issue.

Global Shell

QCCR1D142123 Test button action for RDP and Telnet fails although it successfully works on the server. Windows Global Shell Identify the Windows PID and terminate it using Windows Task Manager or the taskkill command.

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
QCCR1D114639 If you install additional Slice Component bundle instances after patching the SA Core, wayscript versions are set to the version you already have, 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_OPSWwayscripts.
  3. Log in to the SA Core server you identified in step 1
    and execute the following two commands:
    Command #1:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts

    Command #2:
    ./post_after_startup.sh
  4. Apply any required hotfixes to the wayscripts.
QCCR1D132004 Health check fails with mismatched core component version errors (check_occ_up, lnxisoupload, new_platforms, opswbia_upload) Independent Installer None
QCCR1D152571 When you decommission a facility, any scheduled jobs associated with that facility will be lost. Ensure that you have completed, cancelled and/or rescheduled any pending jobs associated with the facility before decommissioning it. Linux Installer None.
QCCR1D161352 Upgrade failed on a slice during OS Provisioning. Independent Installer Restart the upgrade process.

HP has been unable to reproduce this issue. If the same behavior still exists and you can reproduce it, please contact HP Support, referencing QCCR1D161352. Please provide the exact steps to reproduce and/or demonstrate the steps and environment details to HP Support. The current Change Request will remain in HP's database for future reference.

QCCR1D172654 SA should validate /etc/hosts against multiple localhost definitions. RHEL 6.4 core Installer

Remove the following host names from the IPV6 ::1 definition line in the /etc/hosts file:

localhost localhost.localdomain

For example:

Incorrect file content:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

Correct file content:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost6 localhost6.localdomain6

ISM Tool

QCCR1D163521 After the ISM Tool is installed, if commands (such as ismtool.cmd, ismusertool.cmd) are issued, they fail with the following error:

The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.

Windows ISM Tool Install Microsoft Visual C++ 2005 Redistributable Package (x86).

Jobs

QCCR1D121448 When you run the dba_jobs script in the database, the following type of error is displayed:
8412:ORA-06512: at "SYS.DBMS_STATS", line 21271
8413:ORA-06512: at line 1
8433:ORA-12012: error on auto execute of job 68
8434:ORA-20003: Unable to gather system statistics
Linux Jobs None.

Library Framework

QCCR1D150354 During a CBT import/export operation on the Web Services Data Access Engine (twist), the following message appears:

"""SEVERE: Importing Folder: /Home/_underscore Message: name is set to the illegal value '_underscore'.
com.opsware.common.IllegalValueException: name is set to the illegal value '_underscore'.
        at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
        at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)"...
      
Independent Library Framework Rename all folders and users that begin with an underscore (_) before performing an export/import operation using CBT. Alternatively, contact HPSA Customer Support.

Localization

QCCR1D161658 If you chose a Traditional Chinese Windows desktop setting, or you chose a Traditional Chinese profile locale setting in the user interface, your default display language will be Simplified Chinese. This release does not support the Traditional Chinese locale.

Independent Localization None

Model Repository

QCCR1D148020 Incorrect DBTIME on Oracle RDBMS. Independent Model Repository Use the following steps as a workaround:
1) For an existing database, use the following process to change the time zone:

Sqlplus / as sysdba
ALTER DATABASE SET TIME_ZONE = '+00:00';
Shutdown
Startup

Note: The above command assumes that the SA database only has SA schema and no third-party schemas. This solution will not work if there are columns with the timezone parameter defined.

2) For creating a new database in the create database (CreateBD.sql) script, add the following at the end of the file:

CREATE DATABASE truth


SET TIME_ZONE = '+00:00';

OS Provisioning

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 Red Hat 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 - SA Client None.
QCCR1D103602 After you choose Windows as the OS Family, you cannot use the Manage Boot Client (MBC) to create winpexx-ogfs server records in the MBC Single Form because winpe32-ogfs and winpe64-ogfs image types are not displayed in the PXE image drop-down box. Windows OS Provisioning - Backend Use the CSV import to generate the pre-unprovisioned devices.
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.
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
Linux, Solaris, Windows OS Provisioning Do not include any device groups in your OS Sequence.
QCCR1D117539 Unable to stop an OS Build Plan job.

Independent OS Provisioning Wait for the rosh session to time out (the default timeout is 4 hours) or end the rosh session and start a new one. This workaround will only work with a single core, not a mesh.

QCCR1D129619 ESXi DHCP-LESS: DNS Search Domain was not set via the DHCP-LESS value VMware ESXi 4.1 OS Provisioning Backend None. Anything entered in the "DNS Search Domain" field is inserted into the custom attribute as domain=. Therefore, the DNS domain will not be inserted to the ESXi 4.1 system.
QCCR1D131265 Manage Boot Client utility: WAPX sometimes fails at the second step with: 503 Service Unavailable Error Independent OS Provisioning Backend In the Global File System (GFS), use the /opsw/apx/bin/osprov/manage_boot_clients_script.
QCCR1D132628 SUSE Linux Enterprise Server provisioning fails on an HP ProLiant server with a CCISS disk. SLES OS Provisioning For post-SUSE Linux Enterprise Server 10 SP2 provisioning on HP ProLiant servers with CCISS disks, ensure that the <code1>autoyast.xml</code1> file has the partitioning configuration specified as shown below:

<partitioning config:type="list">
<drive>
<use>all</use>
<partitions config:type="list">
<partition>
<mount>/boot</mount>
<size>100mb</size>
<partition_type>primary</partition_type>
</partition>
<partition>
<mount>swap</mount>
<size>1gb</size>
<partition_type>primary</partition_type>
</partition>
<partition>
<mount>/</mount>
<size>max</size>
<partition_type>primary</partition_type>
</partition>
</partitions>
</drive>
</partitioning>

QCCR1D132825/130199 During provisioning in a  non-DHCP environment, Red Hat Enterprise Linux 6 provisioning can become interactive if the HPSAlinux_boot_cd.iso remains connected. Red Hat Enterprise Linux 6 OS Provisioning Backend Eject the boot CD when the server reaches the restart phase or after provisioning becomes interactive.
QCCR1D133153 VMware ESX 4.1 OS Sequence with OS firewall enabled fails with a broken pipe exception during the Agent download phase. VMware ESX 4.1 OS Provisioning The firewall should be disabled during OS Provisioning and re-enabled after.
QCCR1D135080 Spaces at the beginning or the end of rootpw are ignored for ESXi5.
Independent OS Provisioning To use passwords that contain spaces, use quotes (" ") when setting the root_password custom attribute.
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 reprovisioning 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.

QCCR1D144427 When creating an iLO device using the Add iLO operation, the server history mistakenly shows that the device was created by user opsware, and not the user actually performing the operation. Independent OS Provisioning None.
QCCR1D145658

OS sequence provisioning for SuSE Linux 11 x64 on HP ProLiant DL385G5 fails randomly.

SuSE Linux OS Provisioning Set the mpath kernel argument on the server record before running the OS sequence.

QCCR1D146347/141427

Linux 6-OGFS boot failed on HP ProLiant DL380 G4 and DL385 G1. Linux OS Provisioning None
QCCR1D147226 An iLO's realm information is not updated after the iLO is moved from one satellite to another. Independent   Remove the iLO server, then add it again, this time into the correct realm.
QCCR1D155788 OS Build Plan does not reboot into the installer for Red Hat Enterprise Linux 5.0 and 5.1.

Red Hat Enterprise Linux 5.0 and 5.1 HTTP OS Provisioning

There are two possible workarounds:

  • Do not specify "text" and/or "skipx" (graphical install) in the Kickstart file.
  • Use NFS instead.
QCCR1D156536 DHCP-less provisioning fails for Windows Server 2012 Essentials. Windows OS Provisioning Backend None.
QCCR1D160191 SLES11 Guest Customization fails on SCVMM and VMware source template if the source is using Integrated Drive Electronics (IDE) disks.

Microsoft SCVMM and VMware OS Provisioning Add a section into the OS Build Plan (in the step that configures the AutoYaST file) to name the disks as needed (for example: /dev/sda*) or, after the system is installed with SA's default OS build plan, change /etc/fstab to a supported format (for example, change the /dev/disk/by-id to /dev/sda*)
QCCR1D161400

OS Provisioning fails when trying to provision Solaris Version 10u8 or older releases using the Z File System.

 

Solaris X86 OS Provisioning, Backend Use a file system other than the Z File System if you are using Solaris Version 10u8 and older.
QCCR1D162726

OS Sequence Provisioning fails on RHEL 6 PPC with the following error:

Cannot resolve a valid OS media server from OS media resource locator ('nfs://bap.dev.opsware.com/mnt/bap/share/media/linux/RHEL6.3-Server-ppc64').

Linux OS Provisioning Run the import_media script using the IP address of the media server, instead of its hostname.
QCCR1D162834 The following error is displayed when you run an OS build plan, and that build plan is started on a different facility to the one that its target uses:
"Failed to inject required settings.[Errno 2] No such file or directory: '/tmp/osbp_info/'"

Independent OS Provisioning, Backend Start the OS build plan from the same facility that contains its target. This ensures that the plan and its target are using the same database.
QCCR1D164212 The 'Add to Virtualization Manager' step fails during Windows HyperV provisioning with "Agent installation failed on <server> because of a WS-Management configuration error." Windows 2008 R2, Windows 2008 R2 SP1, Windows 2012 OS Provisioning Add a 'Sleep' step for several minutes before the 'Add to Virtualization Manager' step. This will leave sufficient time for the Windows Remote Management service to start.
QCCR1D165305 Provisioning fails with the following ESXi installer timed out error:
"The IP address was not reported. The ESXi installer probably failed."


ESXi 4.1 Update 1 OS Provisioning The ESXi 4.1 Update 1 installer sometimes fails to configure the DNS properly through DHCP. Perform static provisioning or set the media server by IP Address instead of Host Name.
QCCR1D166259

OS Build Plans jobs fail with "Unsupported target OS Osprov Service OS in PROVISIONING/OK". This is happening if the recurring "Agent Communication Test" job coincides with the server being unreachable during the build plan execution, like after the "Reboot" step.

All platforms supported by OS Build Plans OS Provisioning, Backend Bring the failed machine back to the state when the build plan was started, either in the service or productions OS. To recover the lifecycle/state combination for the production OS trigger an agent hardware registration. For the ogfs-agent the lifecycle can be recovered back to UNPROVISIONED only programmatically. Once the lifecycle/state combination is recovered, run the build plan.
QCCR1D168354 If a server's basic input/output system (BIOS) date is older than the initial date on a certificate, the OS build-plan (OSBP) job fails. Independent OS Provisioning Contact HP Support.

Patch Management (Backend)

QCCR1D161643/168655 Cannot download swa_catalog.xml file by using import_hpux_metadata script.

 

HP-UX Patch Management (Backend) Download the swa_catalog.xml file from HP Support site.
Import the downloaded file: /opt/opsware/mm_wordbot/util/import_hpux_metadata -c swa_catalog.xml

Patch Management - HP-UX

QCCR1D157372 SA displays an incorrect message when it tries to remediate an HP-UX server if the following conditions are present:
  1. The "hpuxpatch_dont_supersede" custom attribute is not set.
  2. The patch being remediated has a superseding patch.
  3. The superseding patch is not present in the SA repository.
HP-UX Patch Management None.
QCCR1D165089 Compliance for HP-UX depots not working when multiple depots are attached to the same server. HP-UX HP-UX Patching None

Patch Management - 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 Sun has renamed their Solaris patch clusters - the clusters in your SA Library may not match the cluster names from Sun 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.13, 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.
QCCR1D130601 solpatch_import: Import "Fujitsu Solaris 10 OS Recommended Patch Cluster" fails with 'KeyError: 'patch_order.SS' on a Solaris core. The following error displays when importing a large cluster on an older Solaris core:

bash-3.00# echo Fujitsu Solaris 10 OS Recommended Patch Cluster | ./solpatch_import -a import
Importing patch cluster Fujitsu Solaris 10 OS Recommended Patch Cluster note: didn't find end-of-central-dir signature at end of central dir.
(please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly)

Solaris Patch Management - Solaris - Backend Import a specific patch on your core. See the article from Oracle at https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1020109.1.
QCCR1D132332 After upgrading to SA 10.01, you must manually run update_supplements to see new clusters, such as Fujitsu clusters. Solaris Patch Management - Solaris SA 9.10 provided new clusters (Fujitsu clusters) in the Solaris collection file.
This workaround applies to a mesh that contains different SA cores (such as SA 7.88 and SA 10.01), where the mesh has Solaris patching configured (solpatchdb). After the mesh has been upgraded to SA 10.01, the following command must be manually run on a core server (slice):

/opt/opsware/solpatch_import/bin/solpatch_import -a update_supplements

This command loads the new collection file into solpatchdb.

To see all available clusters, including the new clusters, run the following command:

/opt/opsware/solpatch_import/bin/solpatch_import -a show --available_clusters

QCCR1D137007/152933 Import of Solaris Patch Supplement content may render a false failure error on Fujitsu servers that are missing the appropriate Fujitsu credentials in the solpatch_import.conf file.

Sample error:
live-network-connector:ERROR : Import of content Solaris Patch Supplement version 2.00.00-01 failed. Exception: [PostExecuteError] Non-zero exit (6) for post-execute command '/tmp/tmpgcTtsa/install.sh'.
2011-08-31 19:09:48,823 live-network-connector:DEBUG : Associated metadata: /content/sas/solaris_patching/dd78741ee8ea41718ca70bf0debf3f51.metadata.xml
2011-08-31 19:09:48,824 live-network-connector:DEBUG : {
File "modules/lnc_client.py", line 584, in _importStreams
File "modules/content-handlers/content_uncompress.py", line 87, in import_content
File "modules/lnc_common/ContentType.py", line 111, in do_post_execute
}

Solaris Solaris server patching You can usually ignore this error unless you are trying to import metadata for Fujitsu patches.

If you are trying to import metadata for Fujitsu patches, then you need to enter the Fujitsu credentials into the solpatch_import.conf file located at /etc/opt/opsware/solpatch_import/solpatch_import.conf. Once the credentials are entered, this error message will go away.

QCCR1D137915/153979 You might encounter the following error when attempting to import the Solaris patch supplement:

2011-08-31 19:09:48,823 live-network-connector:DEBUG : }
2011-08-31 19:09:48,823 live-network-connector:ERROR : Import of content Solaris Patch Supplement version 2.00.00-01 failed. Exception: [PostExecuteError] Non-zero exit (6) for post-execute command '/tmp/tmpgcTtsa/install.sh'.
2011-08-31 19:09:48,823 live-network-connector:DEBUG : Associated metadata: /content/sas/solaris_patching/dd78741ee8ea41718ca70bf0debf3f51.metadata.xml
2011-08-31 19:09:48,824 live-network-connector:DEBUG : {
File "modules/lnc_client.py", line 584, in _importStreams
File "modules/content-handlers/content_uncompress.py", line 87, in import_content
File "modules/lnc_common/ContentType.py", line 111, in do_post_execute
}

Solaris Patch Management - Solaris This issue is caused by the fact that Fujitsu recently started requiring username/passwords to download README's from their website.

1. If you have a Fujitsu account, enter the Fujitsu account credentials into /etc/opt/opsware/solpatch_import.conf.

Here are the Fujitsu credential entries in the solpatch_import.conf file:

fujitsu_download_user=<user name>
fujitsu_download_pass=<password>

2. You can also do a temporary workaround to disable the attempted download of Fujitsu account information by editing the /etc/opt/opsware/solpatch_import/collections.xml file to remove the <Fujitsu_clusters> tag information. This will prevent the solpatch_import script from attempting to import the Fujitsu README files. Here is an example of the XML data that will need to be removed:

<fujitsu_clusters>
<download_url>ftp://ftppatch.computers.us.fujitsu.com/fjrs_cluster/${fujitsu_filename}</download_url>
<readme_url>ftp://ftppatch.computers.us.fujitsu.com/fjrs_cluster/README.${fujitsu_basename}</readme_url>
<fujitsu_cluster name="Fujitsu Solaris 10 OS Recommended Patch Cluster">
<file_name>10_Recommended.zip</file_name>
</fujitsu_cluster>
<fujitsu_cluster name="Fujitsu Solaris 9 OS Recommended Patch Cluster">
<file_name>9_Recommended.zip</file_name>
</fujitsu_cluster>
<fujitsu_cluster name="Fujitsu Solaris 8 OS Recommended Patch Cluster">
<file_name>8_Recommended.zip</file_name>
</fujitsu_cluster>
</fujitsu_clusters>

 

QCCR1D138928 Solaris Recommended Clusters cannot be imported into SA when the SA core server has a version of unzip that does not support large Solaris Cluster zip files. SunOS Solaris server patching To resolve this issue, update the unzip tool to v.6.0 on the SA core server before importing the recommended Solaris Clusters into SA.

To update the unzip tool on the SA core server:

  1. Rename the current unzip tool in /usr/bin/ to unzip_OLD.
  2. Copy the unzip file that is shipped with SA under /opt/opsware/bin/.
  3. Paste the new unzip into the /usr/bin directory.
QCCR1D146902/157891 Solaris 11 Patch policies should prevent the user from changing the reboot option to something other than the default option: 'Hold all server reboots until all actions are complete.' Solaris Patch Management - Solaris Always ensure that the reboot option is 'Hold all server reboots until all actions are complete.' when remediating Solaris 11 Patch Policies.
QCCR1D147304 Recommended patches KB979309 and KB2416400 are not shown as recommended in SA, but are present in scanpatchoutput. Solaris Patch Management - Solaris None
QCCR1D156610/159052 When the agent takes a long time to connect to the network after a reboot, the status of the patches that are already installed changes to 'Skipped'. Solaris Patch Management - Solaris None
QCCR1D162554

Installation of Solaris 11 recommended patch policy containing Solaris 11.1 IPS units fails with unsatisfied dependencies.

Solaris Patch Management - Solaris

Solaris 11.1 IPS units should not be present in SA when creating Solaris 11 recommended patch policies. When importing Solaris 11 IPS packages using the sol_ips_import tool, apply the filter ‘-f 5.11-0.175.0’ to exclude Solaris 11.1 IPS packages.  Solaris 11.1 already uploaded into SA should be deleted.

Patch Management - 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
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 To install these patches:
  1. 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.
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.
QCCR1D130284 Install patch Q979309 failed on a Windows 2008 R2 server with exit code 4. Windows Patch Management - Windows - Backend Install KB978601 and KB979309.
QCCR1D131240 If you do not have the SA 9.10 Agent installed on a managed server, the Reboot Server option will not change the server's Reboot Required state from "Yes" to "No". Windows Patch Management - Windows - Backend Upgrade the Agent on your managed server to the SA 9.10 Agent and then reboot the server. The server's Reboot Required state will then accurately display the state as "No".
QCCR1D136931 When running Windows Server 2003 SP2, and when the  target Server has Office Word Viewer 2003, Excel Office Viewer and Compatibility Pack for the 2007 Office System, installed, recommended patches (see below) are not being installed.

Patches:
MS08-052 KB954326 (Office 2007)
MS09-062 KB972581 (Office 2007)
MS10-038 KB982333 (Office 2007)
MS11-023 KB2509488 (Office 2007)

Windows Patch Management - Windows - UI This defect is caused by a fault in the installation-detection logic of one of the patches, which can only fixed by a change in the Microsoft offline patch database. A case has been opened with Microsoft.

QCCR1D144269

The following patches fail to install: KB929300 and KB929300.

Windows Patch Management - Windows - UI Always install the KB929300 patch with the 110806 patch.

Always install the KB2416400 patch with the 2467659 patch.

QCCR1D144556 During an uninstallation of a Microsoft Office security patch an unclear error message is displayed with exit code -5.

Windows Patch Management - Windows - Backend None.
QCCR1D148400/153334 After a Windows Patch Metadata (MBSA) import completes, it takes a long time to update the patches in the library and database information in the Administration page. Windows Patch Management - Windows - Backend None.
QCCR1D155897 During a patch database import, the last Import Summary field does not get populated and shows no data. The cache must be reloaded to correct this.

Windows Patch Management - Windows - Backend None.
QCCR1D157228 Installation of the Q2416400 patch is displayed as having failed with exit code 4 when you suppress reboot during a remediation job. However, the patch is actually installed.
Windows Patch Management - Windows - Backend Manually add KB2467659 to the patch policy. KB2416400 has a dependency on KB2467659.

QCCR1D157363/139856/152927 Occasionally, the following uninstall patch job message is displayed when you manually uninstall a patch using SA: "The Agent reports that this software is not uninstallable."

However, the patch is actually uninstalled.  When you uninstall the patch using the Control Panel > Add/Remove Programs method, the patch uninstalls correctly.

Windows Patch Management - Windows - Backend  
QCCR1D161961 Uninstalling an SP1 patch on Windows 2008 R2 fails with timeout. Windows Patch Management - Windows When the next scan occurs, the status will be updated.

QCCR1D162337 Windows 2k12 software policy remediation fails with the following type of error:

'AGENT_ERROR_PATCH_DATABASE_CERTIFICATE_ERROR'

Windows Patch Management - Windows Import and run the latest (later than October 2012) Microsoft patch CAB file once. You should only have to do this one time.

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 Web Client

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 Web Client None

SA/SAR Reports

QCCR1D82108 In the SA Client in an NA-enabled 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.

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.

Scripts

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.
QCCR1D163487 Python script types are not supported on Unix servers.
Unix Scripts Backend Do not run or choose Python- type scripts on Unix servers.

Search

QCCR1D92244 Searching on extended ascii (that is, European) characters returns no matching results. Independent Search None

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 Module

QCCR1D156389 Users and Groups SMO will not report all the groups that are created on a Windows 2012 Essentials. If user properties are edited, these changes will not be reported by the SMO. This means that audits with U&G rules will not be relevant on a Windows 2012 Essentials. Windows Server Module None.
QCCR1D162746/163940 Cannot create snapshots for Windows Device Manager in Windows 2008 R2 IA64. Windows Server Module None.

Software Management

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
QCCR1D138935/161867 After applying the 9.05 patch, all Solaris 10 x86 remediation jobs failed with the following error:

The operation to download software failed.Execution error: Traceback (innermost last):

File "./base/wayfuncs.py", line 136, in evaluator File " ", line 1342, in ?
File " ", line 1336, in main
File " ", line 1224, in stage File " ", line 610, in download_packages
File " ", line 303, in finishDownload
File " ", line 229, in setProgress
OverflowError: long int too long to convert

Solaris Software Management None
QCCR1D149521 An RHN server error (500 Internal Server) occurs when the rhn_import.conf file is copied from one core to another.

Linux Software Management Change all encrypted passwords in the file into Cleartext and reuse the –hide_passwords option on the new core.
QCCR1D150358/152877 If the Xen server '/' folder has ‘execute’ permissions for only the root user, then any remediation performed by a non-root user will fail. The folder permission should not be restricted to root users.

Citrix Xen Server 6.0.2 Software Management Run chmod 755 /
QCCR1D154714 With YUM versions older than 3.2.22, if the same RPM package is imported multiple times, the analysis might fail, reporting packages as missing.

Windows Software Management - Backend None.
QCCR1D159841 When performing a core upgrade, you might experience conflicts originating from the UNITS and REALM_UNITS tables. In order to continue the upgrade process, you must solve the conflicts using the force resolver script.

Independent Software Management Backend Solve the conflicts with the force resolver script and continue with the upgrade process.
QCCR1D163868 When remediating two different versions of the same rpm package with the install flag set, the older version of the package will be overridden by the newest one, instead of having two different versions of the same package installed on the managed server.

AIX, Linux, Solaris Software Management None
QCCR1D183132

Unintended deletion of certain jobs occurs when you upgrade (or rollback) for jobs scheduled after you install SA 10.01.

The following types of jobs (both pending jobs and jobs that have already been run) are deleted:

  • Remediate jobs (software and patch policies)
  • Software install/uninstall jobs
  • Reboot server jobs
  • RPM/software rollback jobs
Independent Software Management

Follow the steps explained in the Server Automation Alert: Remediation Job Loss During Upgrade/Rollback SRVA 00176
(May 5, 2014)

Software Repository

QCCR1D131751 HP Server Automation 9.10 configurations that use a Solaris machine as the Network File System (NFS) server may encounter unexpected behavior and unreliable performance. Due to known instability issues with Solaris NFS, this configuration should be avoided. The recommended configuration is a Linux NFS server, which works reliably with either Solaris or Linux clients. Solaris Software Repository The recommended configuration is a Linux server as the NFS, which works with either Solaris or Linux machines as clients.
QCCR1D152739 During Secondary Core Model Repository installation, the following warnings are seen in the installer log:

ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."FIBREFABRICELEMENTS" created with compilation warnings
ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."AGENTPACKAGE" created with compilation warnings
ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."STORAGEDEVICE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TRUTH"."RESOLVEDUPLICATEWWN" created with compilation warnings

Red Hat Linux Server 5 Software Repository The warnings occur due to the Oracle RDBMS's improper object import order or due to dependencies on others objects. Although the SA Installer corrects these issues by compiling all objects after import, these warnings may still be seen in the installer log. You can ignore the Oracle RDBMS warning messages in the installer log.

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 Storex does not support VMWare hosts that have Virtual Machine Disk (VMDK) volumes created on Network File System (NFS) storage. Independent Storage Host Agent Extension Contact your Server Automation administrator.
QCCR1D142746 Storage Visibility Automation does not support ESX Servers on the Storage Host Agent. Independent Storage Host Agent Extension None
Bug ID: 149406 / QCCR1D 60760 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 / QCCR1D 61061 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 / QCCR1D 63275 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 / QCCR1D 63370 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 / QCCR1D 64296 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 operating system, 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 / QCCR1D 65772 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 / QCCR1D 66325 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 / QCCR1D 66830 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: 157579 / QCCR1D 68933 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 / QCCR1D 70277 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 / QCCR1D 70510 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 / QCCR1D 70934 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 / QCCR1D 76305 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: 167103 / QCCR1D 78457 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.
Bug ID:168889 / QCCR1D 80243 If you disable a volume in Veritas DMP and subsequently take a new Storage Host Agent Extension snapshot, it appears as if 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.

Reporting

QCCR1D144794 When you try to change the filter from 'Default' to 'Equals' in a report section (when selecting Server by Model report), you will see the following error:

java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: BEA1-468A20F38EF4DF26344B; nested exception is:
javax.transaction.HeuristicMixedException: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: Closed Connection))

In addition, the Oracle trace log will have messages similar to the following:

ORA-07445: exception encountered: core dump [evaopn3()+135] [SIGSEGV] [ADDR:0x4] [PC:0x874EC17] [Address not mapped to object] []

This error is happening due to a bug in Oracle's Optimization logic, which dumps core and closes the session when there is more than one function-based index on a column. 

Independent Reporting Download and install the Oracle patch 13369579.

UCMDB

QCCR1D155278 Tellconector enable/disable scripts need to validate the options before they run.

Independent UCMDB None.
QCCR1D155279 Tellconector enable script shouldn't auto assign the values to local if the script is run without any options. Independent UCMDB None.
QCCR1D156338 Configuration files are overwritten when SA is upgraded between builds.

Independent UCMDB Back-up the files before upgrading to make sure that the existing configuration files are saved.

Upgrade

QCCR1D142939 Unclear when to use script: windows_2008_R2_fix_script.pyc.

Windows Upgrade When migrating from SA 7.8 to SA 9.1x:

  • Upgrade to 7.87 first.
  • Migrate all 2008 R2 servers using the script: windows_2008_R2_fix_script.pyc
  • Upgrade to 9.1x.

When migrating from SA 9.0 to SA 9.1x:

  • Upgrade to 9.04 first.
  • Migrate all 2008 R2 servers using the script: windows_2008_R2_fix_script.pyc
  • Upgrade to 9.1x.

Usability

QCCR1D166334

The SA-installed Oracle RDBMS modifies the /etc/sysconfig/selinux file and inserts the following entry for SELINUX regardless of whether a previous entry exists.

#SAS Oracle parameters begin
SELINUX=disabled
#SAS Oracle parameters end

Linux Usability

If multiple entries exist in the /etc/sysconfig/selinux file, only keep the entry that is shown in the description, but make sure that the value for SELINUX is 'disabled' or 'permissive', not 'enforcing'.

Virtualization

QCCR1D141907 If you configured the number of cores per socket using the native vSphere client, and modify the number of virtual processors with a Modify VM job in SA, the CPUs might end up in an invalid configuration.  When you edit the CPU settings in the native vSphere client, this error, “Number of cores per socket cannot be greater than number of virtual CPUs” occurs when the configuration is invalid.

The native vSphere client multiplies the number of virtual sockets by the number of cores per socket to determine the Total CPUs.  SA only discovers and sets the Total CPUs (from the Virtual Processors field). 
Examples when the VM has 2 cores per socket: 

  • Set SA’s Virtual Processors to 8, there will be 4 virtual sockets and 8 total CPUs. 
  • Set SA’s Virtual Processors to 1, the number of virtual sockets will be 1 and that results in an invalid configuration.
VMware vCenter Virtualization If the number of cores per socket for a VM is greater than 1, and you want to modify the CPUs:

  1. From SA, set the number of Virtual Processors as a strong multiple of the number of cores per socket.
  2. Or, use the native vSphere client to modify the CPUs.
QCCR1D142816 HP-UX virtualization APX displays incorrect message when user tries to start a vpar. HP-UX HP-UX virtualization None
QCCR1D150577

Cloning a powered-on VM running Windows on some earlier versions of VMware ESX/ESXi fails during the Guest Customization step.

If you are:

  • Running a version of VMware before ESXi 4.1 Update 2 or ESXi 5.0, and
  • the VM is running Windows, and
  • the VM has VMware guest tools installed, and
  • the VM is powered on, and
  • you try to clone the VM, then:
The clone operation can fail in the Guest Customization step.

This occurs because of a VMware problem that has been resolved in ESXi 4.1 Update 2 and ESXi 5.0 Update 1. For details, see the Resolved Issues listed in the VMware ESXi 4.1 Update 2 Release Notes or the VMware ESXi 5.0 Update 1 Release Notes.
VMware vCenter, Windows Virtualization - VMware To resolve this issue, you can do either of the following:
  • Upgrade to a later version of VMware ESXi where this problem is fixed. For details, see the Resolved Issues listed in the VMware ESXi 4.1 Update 2 Release Notes or the VMware ESXi 5.0 Update 1 Release Notes.
  • Power off the VM before cloning it.
QCCR1D153021 If you clone a Windows 2008 VM or deploy a VM from a Windows 2008 VM Template using static-to-static configuration, the source’s IP Address is not removed from the new VM and the gateway is not set.

The problem occurs when:

  • Clone VM or Deploy VM from Template
  • The source is Windows 2008 32-bit or 64-bit
  • The source has a static IP address

Although the source’s IP address is not removed, the new VM still works because it marks the correct IP address as preferred.

Although the gateway is not set, the agent can still communicate with the core.  However, DNS will not work.

VMware vCenter, Windows Server 2008 32-bit/64-bit Virtualization None.

QCCR1D155406 When SA discovers SCVMM VMs or Templates that were already agent-managed, SA ends up with one agent-managed device record and one virtualization-managed device record, both for the same device. This occurs because device correlation does not work for SCVMM VMs or Templates.

SCVMM does not discover the SMBIOS UUID of their VMs and Templates.  SA uses the SMBIOS UUID to correlate the newly discovered device or template with the agent-discovered SMBIOS UUID property. 

Microsoft SCVMM Virtualization Backend Device correlation works when you install agents after discovery.

Device correlation works when you do the following from SA:

  • Create VM with OS Build Plan
  • Convert VM to VM Template
  • Deploy VM from VM Template with Guest Customization
It is possible to merge two device records using the com.opsware.server.serverService.merge function in twister.
QCCR1D157328

Your job fails with the following error:

The host server or the Virtualization Service is not reachable. Check the network communication and retry the operation. Ensure server hosting Virtualization Service has SA agent installed.

This may occur in several scenarios, here are a few examples:

  • The SCVMM server is down.
  • You have a large SCVMM inventory and you are running concurrent reload data jobs.
  • You perform Delete VM, Delete VM Template, or any power control operation on a large number of objects in one job.
  • You have many concurrent jobs running against the same SCVMM.
The reason is that SA is unable to connect to the SCVMM server. Or, the maximum number of connections to the SCVMM server through the SA Agent has been reached.
Microsoft SCVMM Virtualization Backend Check the following:

  • That the host server is running and has a valid network computer name.
  • The Virtualization Service is running, is DNS resolvable, and has proper network communication.

Contact HP Support.

QCCR1D157368/160408 In the Add Virtual Servers HP-UX Virtualization Manager screen, if you enter a specific HP-UX machine name into the search field of the IP Address/Hostnames choice, no list of HP-UX machines is generated.

HP-UX HP-UX Virtualization

In the Add Virtual Servers HP-UX Virtualization Manager screen, click Explicit IPs/Hostnames, then choose All from the drop-down menu. A list of all the HP-UX machines is displayed. Select the machine you are looking for and click Add Server.
QCCR1D157587 When you migrate both host and storage for a VM in SCVMM, and you select a host in a Cluster (in SCVMM the Transfer Type is Cluster), then the settings for the Storage and Network steps are ignored. SA does not discover the Transfer Type property for the hosts.

When you do a cluster migration in SCVMM, SCVMM does not offer the option to set additional migration parameters.

Microsoft SCVMM Virtualization Backend None
QCCR1D158199

Virtual distributed switches cannot be discovered using the VMware virtualization service. As a result, a virtual machine's NIC connections to virtual distributed switches will not be visible in the SA Client or in backend objects.

VMware Virtualization - Backend (VMware) None.

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
QCCR1D168519*** LRUCache WaySessionUtils.srcache can cache empty results. Independent Web Services Data Access Engine (twist) Contact HP Support for information on a hot fix that addresses this issue.
QCCR1D168828 API version label should to be updated. Linux Web Services Data Access Engine (twist)

Use the following methods to find the SA version running on the Core server versions:
ServerAPIVersion() : 190.0.2
ServerVersion() : 45.0.38347.0

Work Load Manager (WLM)

QCCRID163928 For recurring non-blocked WLM jobs, once the child job is run, SA determines if the parent job should expire by comparing the end date with the next fire date. The status of the parent job is updated to EXPIRED if the next fire date is beyond the end date. For recurring blocked WLM jobs, however, when the child job completes its run, SA does not determine the expiration of the parent job. If the approval notification for a BLOCKED job is not setup at all or setup incorrectly, the child job will remain in the BLOCKED state and no computation will be made to determine the status of the parent job.

Independent Work Load Manager None
QCCR1D166350

Jobs remain with a status of Active, even though their associated tasks show a status of Success.

This known issue is applicable only to Workload Manager framework-based jobs, such as V12n or iLO.

Independent Work Load Manager This issue occurs only in multi-core mesh installations where the SA Jobs are being approved using Operations Orchestration on all the cores of the mesh. To work around this issue, setup OO workflow only on the primary core of the mesh.


*** Known issues denoted with three asterisks (***) might have a Hot Fix available. Contact HP Support for more information.

 

Back to the Table of Contents



Fixed Issues

The Fixed Issues table includes issues that:

The table lists issues first by subsystem, then numerically within each subsystem.

QCCR1D Symptom/Description Platform

AAA

QCCR1D167959/168243 The /opt/opsware/twist/ldap_config.sh file does not support multiple-base DN searches. Linux
QCCR1D168463/168467 WRITE_PERSISTENCE_ERROR messages in the Web Services Data Access Engine logs. Linux

Audit And Compliance

QCCR1D159358/171123 ttlg/rosh handshake timeout can occur for large saved scripts over slow networks. Windows
QCCR1D166532/166534 Duplicate audit rules are filtered out when performing audits, causing missing audit-compliance results in BSAE and the SA Client. Windows
QCCR1D167727/167728 After applying hotfix for issues described in QCCR1D152831, exporting audit results to CSV no longer changes commas within the audit rules to semicolons, resulting in innacurate reports.  Windows
QCCR1D168072/168303 Audit job reports an out-of-compliance status, although the expected value in the registry key is correct. Windows

Compliance Dashboard

QCCR1D164840/164888

Compliance information should accurately reflect the compliance of policy items that are duplicated across multiple policies.

Linux

Data Access Engine

QCCR1D166753/166754 The object HPUXProductUnit is missing the remove_flags field. HPUX

DCML Export Tool (DET)

QCCR1D168103/168808 CBT Import from air-gapped Development Core to Production Core fails. Linux
QCCR1D167377/167382 CBT checksum algorithm is slow and uses a large amount of memory. Linux
QCCR1D167883/168019 The -nu option  in the command-line invocation of DET (CBT) (which checks for duplicates) still compares the checksum, but fails to compare file sizes, resulting in hash collisions and unnecessary checksum calculations. Linux

Device Groups

QCCR1D168478/168481 Recalc job cannot be disabled without disabling the Web Services Data Access Engine. Linux
QCCR1D168737/168738 After applying fix from QCCR1D153505 device group membership shows group ID instead of name. Linux

Gateway

QCCR1D166041/166045 Mesh-wide outages occur and the proxied TCP flows are halted due to an opswgw tunnel disruption. Allow the opswgw setting to be customer configurable. Linux

Global File System

QCCR1D168562/168565 Network-attached storage (NAS) interface links are broken in the OGFS. Linux
QCCR1D164325/168651 Need to document a list of all Global Shell commands (and an explanation of each) to access the SA Client. Linux
QCCR1D168310/168325

Audits are failing, with each client throwing the following type of error:

An internal exception of type
com.loudcloud.opsware_common.errors.OpswareError with message
OpswareError: Executing Audit failed [ module:
com.opsware.acm.way, method: calculateAuditBasePath, line:
110, hostname: ajaxlsac9000.corp.citistreet.org, timestamp:
2013-06-17 18:52:19.6, messageKeyOrder: msg, msg:
java.lang.NullPointerExceptionFound in: com.opsware.acm.way.
SnapshotComplianceWayHandler ]

Linux

Installer

QCCR1D168302 You receive the following error when you try to install SA from the primary ISO media:
/mnt2/primary/disk001/opsware_installer/hpsa_install.sh
You cannot run hpsa_install.sh from /mnt2/primary/disk001/opsware_installer
Linux
QCCR1D168038 Too many world-writable files under /opt/opsware. Independent

Jobs

QCCR1D165832/165877 When you schedule an OGFS pytwist script to run more than 30 days in advance, the job runs, but then fails with a "Missing fields ([token])" error. Linux
QCCR1D170782/170783 Incorrect results displayed in the results window after a remediation job. Independent

Library Framework

QCCR1D129781/170792 The SA Client uses excessive amounts of local PC resources (memory & CPU), eventually causing the PC to cease up during software-package updates. No errors are generated. Windows

OCC Client Framework

QCCR1D168719/168721 PackagePropertiesPanel validation is too aggressive and inefficient when editing package scripts. Independent
QCCR1D165483/168277 Advanced search of servers with large result set can cause an out of memory (OOME) incident if sorted on the custom-field column. Independent
QCCR1D167741/168973 An audit does not show device groups as targets, even though the device group shows the audit attached in its properties. Independent

Patch Management

QCCR1D168064/168638 Missing instructions on AIX patch importer in documentation.
Resolution: Added instructions on AIX patch importer to Unix chapter of UG: Server Patching for 10.1.
AIX
QCCR1D83726 Deployment of Windows and Red Hat patches should be faster. Red Hat, Windows
QCCR1D165623/167025 The rhn_import script does not support the Auto-Update-like feature. Red Hat

Power Shell Integration

QCCR1D161369/166840 Cannot run Powershell v3 scripts. Windows
QCCR1D161368/166843 Powershell custom scripts in an audit are compliant, even if the script itself fails. Windows

Software Management

QCCR1D166319/166320 Importing a depot file without machine_type set in the catalog/INDEX file results in an "Invalid depot file" error Linux
QCCR1D168451/168452 Solaris Packages with response files fail to install. Solaris
QCCR1D168231/168525 You receive errors similar to the following when you execute remediation and software installation jobs:
The operation to download software failed.Execution error: Traceback (most recent call last): File ".\base\wayfuncs.py", line 136, in evaluator File " ", line 2940, in ? File " ", line 2934, in main File " ", line 2738, in stage File " ", line 1162, in download_packages UnboundLocalError: local variable 'client' referenced before assignment
Linux
QCCR1D165183/170082 Remediation data structures contain too much redundant information, and do not scale well. Red Hat
QCCR1D167731/167732 Requesting a more efficient method to snapshot RHN channels. Red Hat
QCCR1D164689/164691 The option "Suppress all server reboots" is not set correctly in install software jobs. Linux
QCCR1D164878/164879 The SA Client does not correctly display remediation jobs created with the pytwist script. Linux
QCCR1D170632/170634 SA Client cannot proceed if it is browsing a folder with more than 100K objects. Linux

Storage Database Scanner

QCCR1D157481 Performing Oracle DB scan against a group of Oracle servers causes a deadlock and produces a trace file. Linux, Solaris

Web Services Data Access Engine

QCCR1D167739/168529 getServerVO permissions are not escalated during an audit execution, Independent
QCCR1D165724/169177 Some audits are not running at the scheduled time. When these audits are run manually, the following error is displayed:
RemoteExeption occurred in server thread; nested exeption is : java.rmi.RemoteException: EJB Exception:;nested Exception is : java.lang.NullpointerExeption
Linux, Windows


Back to the table of contents



Documentation Information

This section discusses documentation information for this release.

Note: The most up-to-date information for this release can be found in the latest version of the release notes, guides, and white papers, located at: http://support.openview.hp.com/selfsolve/manuals.

Documents Relevant to This Release

In addition to the 10.0 guides on the Self Solve website, the following white papers and guides are relevant to this release:

Note: Some of these guides and white papers were released in earlier patches, but are still relevant to SA 10.01.

Documentation Errata

This section contains corrections for existing documentation.

SA 10.0 Administration Guide

* Chapter 2: SA Core and Component Security

Page 104, Recertifying SA Cores section - replace the entire section/steps with the following:

Recertifying SA Cores

Note: You must clear all backlogs and conflicts on your Multimaster Mesh before you start a core
recertification.

To recertify SA Cores, perform the following tasks:

1. Ensure that you are classified as a Core Recertification User. If not, see your SA System
Administrator.

2. Log on to an SA Core host.

3. Change directory to /opt/opsware/oi_util/OpswareCertTool/recert_utils/.

4. Edit corerecert.conf to ensure that the information is correct for your environment.

5. Run: corerecert --status to ensure Core Recertification is not currently in progress.

6. Run: discover_mesh -p to make sure the Core Recertification Tool can correctly detect your Mesh setup.

7. Run: corerecert --phase 1 from the command line to initialize Core Recertification.

8. Monitor the progress on screen by running: corerecert --status until it has indicated Phase 4 is in progress.

9. Run: corerecert --phase 4 from the command line to start Phase 4, which appends a new Agent CA to all the Agents.

10. Monitor the progress on screen by running: corerecert --status until all the Agents have successfully had a new agent CA appended.

Note: This step could take days depending on your maintenance windows and the Agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 9 on page 105. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recert job for the successful facilities.

11. Run: corerecert --phase 6 --doit from the command line to start Phase 6 of the core recertification.

12. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. At this point, you must work with the SA System Administrator to restart the mesh.

Note: This step could take days depending on your maintenance window. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 11.

13. After the mesh has successfully restarted, run: corerecert --phase 6 from the command line to continue phase 6.

14. Monitor the progress on screen by running: corerecert --status until phase 7 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 13 on page 106.

15. Run: corerecert --phase 7 from the command line to start phase 7.

16. Monitor the progress on screen by running: corerecert --status until phase 8 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 15.

17. Run: corerecert --phase 8 from the command line to start Phase 8, which recertifies all the Agents.

18. Monitor the progress on screen by running: corerecert --status until all Agents have successfully been recertified.

Note: This step could take days depending on a customer’s maintenance windows and the agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 17. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.

19. Run: corerecert --phase 9 from the command line to start phase 9. The Core Recertification Tool prompts you to confirm that you want to begin phase 9. Press y to continue.

20. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 19. At this point, you must work with your SA System Administrator to restart the mesh.

Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 19 on page 106. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.

21. On the base Slice core server:

a) Issue the following commands:
touch /var/opt/opsware/crypto/twist/upgradeInProgress
/etc/init.d/opsware-sas restart

b) Wait till the restart successfully finishes, then

c) Restart the rest of the mesh.

22. After the mesh has successfully restarted, the Recertification User must run: corerecert --phase 9 from the command line to continue phase 9.

23. Monitor the progress on screen by running: corerecert --status until Phase 12 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 22

24. If you do not intend to remove the Agent CA, skip to step 26. Otherwise, run: corerecert --phase 12 from the command line to start phase 12, which removes the old Agent CA from all the Agents.

25. Monitor the progress on screen by running: corerecert --status until the old Agent CA has removed from all the Agents.

Note: This step could take days depending on customer’s maintenance windows and the agent availability. If you encounter any errors during this stage, resolve the errors and go back to step 24. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.

26. Run: corerecert --phase 13 --doit from the command line to start phase 13. If you do not want to remove the old CAs, a Mesh restart is not required in this phase.

27. Monitor the progress on screen by running: corerecert --status until it indicates mesh_restart_pend. At this point, you must work with the SA System Administrator to restart the mesh.

Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 26.

28. After the mesh has successfully restarted, run: corerecert --phase 13 from the command line to continue phase 13.

29. Monitor the progress on screen by running: corerecert --status until it indicates that Core Recertification has completed successfully.

SA 10.00 Standard/Advanced Installation Guide

* Chapter 4: "Pre-Installation System Requirement Checks", Item #6: Check the Free Disk Space Requirements (page 49), Table 9: SA Disk Space Requirements: the disk space requirements have changed to reflect changes for the CORD patches and hotfix installations.

Several directories are created under the /var/opt/opsware and the /opt/opsware directory to facilitate the patching. The diskspace requirements listed below have been increased to handle the patch media requirements:

/opt/opsware 25 GB
/var/opt/opsware 20 GB

SA User Guide: OS Provisioning

* Chapter 5, "Special Attributes for the CLI and CSV Input Form",  Table 12, page 127:

The table entry for the "facility" special attribute should be changed to note that it is the Facility ID that is required, not the Facility Name.

SA Support and Compatibility Matrix

Footnote 5 under the Core and Satellite Server Support table was incomplete.

Original:
5     For RHEL5 U9, the latest update version kernel 2.6.18-348.16.1.el5 or above is required.

Changed to:
5     IMPORTANT Note about Red Hat 5.9, 6.3 and 6.4: If you are running a default RedHat 5.9, 6.3, 6.4 kernel, you must upgrade the kernel to a version that no longer has an issue with the SO_REUSEADDR socket semantics. This can be accomplished by installing the latest kernel from the RedHat errata advisory, or installing the next release of RedHat Linux, as described below:

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.



Legal Notices

 

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-2013 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.

Release-Notes Updates


New Publication Date Change
5/10/2014 Added information about job loss during upgrade or rollback in the upgrade and rollback sections, and in the Known Issues Table, issue QCCR1D183132.
   
   

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