HP Server Automation Release Notes

Software version: 9.16

Software Release Date: March 2014

Documentation Release Date: March 14, 2014

These Release Notes provide an overview of the changes made to HP Server Automation in this release. They contain important information not included in the manuals or in online help. Check the HP Self-solve documentation portal for the most current release notes.

 

Up-To-Date Documentation

Additionally, all SA 9.1x guides are compiled and catalogued for easy access in the SA 9.1x All Manuals downloadable zip file.

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:

New in This Release

Installation

Known Issues

Fixed Issues

Deprecated Features

Documentation Information

HP Software Support

Legal Notices



New In this Release

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

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


New Qualified Managed Platform Support and Browser Support


Qualified Managed Support

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, also at: http://support.openview.hp.com/sc/support_matrices.jsp.

Check the HP Software Product Manuals portal for the most current matrices.

Browsers

This table shows browser support information for this release.

  Windows XP Windows Vista Windows 7 Windows 2008 Windows 8 Windows 2K8
Chrome

x

x

x

x

x

x

Firefox

x

x

x

x

x

x

IE 6.0

x

 

 

x

x

x

IE 7.0

x

x

 

x

x

x

IE 8.0

x

x

x

x

x

x

IE 9.0

x

 

x

 

x

x

IE 10.0

(Compatible Mode)

x

 

x

 

x

x

 


New Installation Preparation Instructions for SA 9.1x Series

Make sure you follow these steps before you install SA:

  1. Mount the patch ISO file to a directory. 
  2. Then copy the entire content of the directory mentioned in step 1 to a writable file system. 
    This file system must have the equivalent free-disk space equal to double the size of the ISO file plus 1 GB. For example, if the ISO file is 4 GB, make sure the file system has at least 9 GB of free-disk space available.
  3. Run the patch installation scripts as explained in Script Running Order, but run the scripts from the writable directory, not from the original mount location.

List of New Functionality



Installation

This section describes the installation procedure.

General Information


Script Running Order

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

SA Script Running Order - Upgrade

Upgrade From

To

Script Running Order

9.10, 9.10.01, 9.10.02, 9.11, 9.12, 9.13, 9.14, 9.15

9.16

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

SA Script Running Order - Rollback

Roll back From

To

Script Running Order

9.16

9.10

  1. patch_opsware.sh
  2. patch_database.sh

Migrating from SA 7.8 or SA 9.0 to SA 9.16


Migrating Order

When migrating from SA 7.8 to SA 9.1x:

When migrating from SA 9.0 to SA 9.1x:

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.

Database Schema Update Procedure

The script run during this procedure makes required changes to the Model Repository including adding required tables and objects.

  1. Mount the SA 9.16 distribution. Invoke patch_database.sh on the Model Repository host:
    All SA Core Servers must have their time zone set to Coordinated Universal Time (UTC). In a RAC environment, all RAC nodes must have the exact same time.

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

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

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

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

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

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

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

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

    [timestamp] Done with component Opsware SQL patches.

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

    [timestamp] Opsware Installer ran successfully.

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

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

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


This error is invalid and you can disregard it.

Patch Installation Procedure

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

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

Installation Steps

Perform the following tasks to install SA 9.16:

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

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

    Usage : patch_opsware.sh [--verbose]

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

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

      Enter i at the prompt to begin the installation.

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

      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: u

      Enter u at the prompt to begin the upgrade.

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

    The installer displays the following upon completion:

    [<timestamp>] Done with component Opsware Patch.

    [<timestamp>]

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

    [<timestamp>] Opsware Installer ran successfully.

    [<timestamp>]

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

Software Repository Content Upgrade

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

General Information

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

Upgrading the First Core Content

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

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

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

    The following menu is displayed:

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


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

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

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

Rolling Back the Patch


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

Steps to Rollback the Patch

To roll back SA 9.16 to SA 9.10, invoke the script:

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

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

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

Enter r at the prompt to remove the patch.

Note:

Rolling Back the Database Schema Update

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

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

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

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

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

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



Post-Installation Tasks

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

Installing Red Hat EL 5.9

If SA 9.16 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:

  1. Set the following kernel parameters:
    sysctl net.ipv4.tcp_tw_recycle=1
    sysctl net.ipv4.tcp_tw_reuse=1
  2. 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

  3. 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 SA 9.16, 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 to version 9.1X, wayscript versions are set to version 9.10 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 9.16, as the settings are set to the SA default during installation or upgrade.

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

Upgrading SA Agents

Since 9.11, SA Agents have used Python 2.4.4.

After you upgrade to SA 9.16, you should also upgrade to the 9.16 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.16 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.16
    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.16_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 high severity issues from SA versions 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, and 9.16. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.

Known Issues

QCCR1D Subsystem Platform Symptom/Description Workaround

Agent

QCCR1D156924/167887 Agent Linux; Solaris Software policy remediation of multiple packages with reboot option fails at install stage with batchbot error: The operation to install or uninstall software failed.  Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue.
QCCR1D159580 Agent Windows The VMWare Virtual Network Adapters installed with VMWare Server on Windows uses the same MAC addresses by default, causing agent registration to fail with the following message:

ERROR: spin.notUniqueInDatabase - SA was unable to locate the record for this server in the database because more than one record already exists with the MAC address.
Use the --force_new_device option and pass it as a parameter to the agent installer.

QCCR1D168321/168321 Agent Solaris

Fujitsu hardware running on Solaris servers reports a partial serial number if the gp-serial number is enclosed in single quotes.

Contact HP Support for information on a hot fix that addresses this issue.

Application Configuration Backend

QCCR1D160790 Application Configuration Linux When loading the configuration data for the CML template containing two blocks, configuration data for the second block is loaded into the first block. Set the delimiter="[" for the first block to instruct the CML parser that the first block ends when it reaches the start of the second block:
@*firstfield;unordered-string-set;;delimiter="["@.

Command Engine (Way)

QCCR1D177571 Command Engine Linux SA installation on a core fails with the following error:
Archive:  /mnt/90/packages/././OPSWwayscripts-40.0.0.0.71.2.zip
inflating: wayscripts.archive
[Oct-11-2013 15:02:08]  Running script wayscripts/post.
Installing Wayscripts:
...
Installing __global__.adt_deploy_agents.bat (version opsware.34.3)
...
Traceback (most recent call last):
File "./util/wayscript_installer.py", line 878, in ?
...
self.append(_stringify(data))
...
timeticks:  None
waybot.verifyUpdateFailure
Wayscript installation failed. Archive left in /var/tmp/oitmp/wayscripts.archive.
[Oct-11-2013 15:02:14] Component installation script encountered an error (exit status 1)
[Oct-11-2013 15:02:14] Exiting Opsware Installer.
To install without this error:
1. Copy the following directories from a slice that is already recertified to the new slices you plan to add to the recertified mesh:
/var/opt/opsware/crypto/waybot/archives/
/var/opt/opsware/crypto/wordbot/archives/
2. Rerun the installer:



Gateway

QCCR1D172459 Gateway Linux During monitoring of Gateway flows from the SA Web Client, one or more connections remained in the ACK state with InFlight=-1 until the cgws is restarted. Restart the core gateway service.

Global File System (Spoke)

QCCR1D162289/162450 Global Filesystem/Shell Backend Independent Deadlock errors occur when you run a storage snapshot ((Storage --> Inventory). None.
QCCR1D167608 Global Filesystem/Shell Backend Linux Failures running OGSH commands in SA from OO. Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue.

Model Repository (Truth)

QCCR1D172195 Model Repository Independent A secondary core created from a SA9.14/SA9.15 primary core creates 2 jobs for AAA user in dba_jobs table. Run the following on the secondary core. If you have a RACed environment then run this on one of the RACed nodes.

$ sqlplus "/ as sysdba"
SQL> grant create session to aaa;
SQL> connect aaa/<aaa_password>

#You should see 2 rows in the result set for the SQL below
SQL> select job, what from user_jobs;

#below SQL will give you the job# of the duplicate job
SQL>select job from user_jobs where what like 'gather%stats%' and job not in (select max(job)
from user_jobs
where what like 'gather%stats%'
group by priv_user, what);

#below SQL will delete the duplicate job. Replace the ‘insert_job_no_from_previous_sql_here’ with the value from previous step
SQL> execute dbms_job.remove(insert_job_no_from_previous_sql_here);

#You should see only 1 row in the result set for the SQL below
SQL> select job, what from user_jobs;
SQL> connect / as sysdba
SQL> revoke create session from aaa;

Check the SysDiag test. The error of incorrect job count should not be there.
QCCR1D172371 Model Repository Independent Secondary core creation on Oracle 11.2.0.3 RACed environment ran into ORA-01031: insufficient privileges: grant execute on dbms_utility to data_owner. Apply Oracle PSU 11.2.0.3.7 and re-run the SA installer.

OS Provisioning (Backend)

QCCR1D120072/161507 OS Provisioning Backend Independent

The Manage Boot Client  (MBC) creates a record when both satellites are running , but if one of them is no longer running, the MBC fails with the following error:

00:01:22:EF:0F:99FAIL 2140101 hpsatest2 Problem setting auto prov for this MAC
RemoteException: EJB Exception:; nested exception is:
java.rmi.RemoteException: Error from remote (3032): connect to Agent failed (Connection refused)

Remote Traceback:
File "ServerRequest.java", line 205, in sendReceive

invokeServlet
File "ServletStubImpl.java", line 292, in execute

Remote Traceback:
File "OSSequenceServiceBean.java", line 171, in runOnServer
None.
QCCR1D159441 OS Provisioning Backend Linux RHEL/SLES builds fail with the following error:

RHEL : Agent installation failed with return code of: 1024
SLES: Agent installation failed with return code of: 32512
Contact HP Support for information on a 9.16 hot fix that addresses this issue.
QCCR1D165440 OS Provisioning Backend Linux

Cannot install any Gen7 or Gen8 Servers that have AMD CPU's during the assisted installation process.

The final line during the installation process is:

Fixing recursive fault but reboot is needed!
None.
172963 OS Provisioning Backend Linux OS Provisioning fails for Windows Server 2012 VMs during the specialized step if you specify more than one partition in an unattended file, and the first partition is too small for the OS to fit. Ensure the partition layout will not change the %SystemDriver% environment value.
QCCR1D174726 OS Provisioning Backend Windows Winpe64-OGFS no longer contains drivers for BCM5709C NetXtreme II GigE (14e4:1639). Use the 9.14 WIM image or update the current wim images with the needed drivers. For details see the KM1405856 knowledge article at
http://support.openview.hp.com/selfsolve/document/KM1405856.
QCCR1D177204 OS Provisioning Backend Windows OS Provisioning of WinPE images will fail about 10% of the time when using a port channel or two bonded NICs. Disable the second NIC in either the switch or WinPE image

Patch Management (Backend)

QCCR1D102713 Patch Management Backend Independent 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. None.
QCCR1D137915/152933 Patch Management Backend Solaris 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
}
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.
QCCR1D144269 Patch Management Backend Independent The following patches fail to install: KB929300 and KB929300. If performing an individual patch installation, the following patches must be installed as pairs in order for the job to succeed.
KB929300 -- must be remediated along with 110806.
KB2416400 -- must be remediated along with 2467659.

For these pairs, if the patch installation job contains one of the patches in the pair but does not contain the other, the job will fail.
QCCR1D157228 Patch Management Backend Independent Installation of the Q2416400 patch fails with exit code 4 when you suppress reboot during a remediation job. However, the patch is actually installed. Manually add KB2467659 to the patch policy. KB2416400 has a dependency on KB24676.
QCCR1D157363 Patch Management Backend Windows 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.  None
QCCR1D157372 Patch Management Backend HP-UX SA displays an incorrect message when it tries to remediate an HP-UX server if the following conditions are present:
* The "hpuxpatch_dont_supersede" custom attribute is not set.
* The patch being remediated has a superseding patch.
* The superseding patch is not present in the SA repository.
None.
QCCR1D161643/168655 Patch Management Backend HP-UX Cannot download swa_catalog.xml file by using import_hpux_metadata script. 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.
QCCR1D174155 Patch Management Backend AIX

A master software policy with embedded child policies is remediated and displays the following error:

"Install tivoli.tsm.client.oracle.aix.64bit-5.5.2.0 Will Not Install" the reason being "Fileset is missing requisite bos.rte v=5 r>0"

Upgrade the tivoli.tsm.client.oracle.aix.64bit package to version 6.3 , which has vendor support for AIX 7.1.

QCCR1D177309 Patch Management Backend Linux

Windows Patch compliance scans might fail with the following traceback:
tb_str: Traceback (most recent call last):
File "/var/opt/opsware/waybot/scripts/opsware.patch_compliance~45.0.1", line 561, in updateSingleDevice
compliance_result = tp.auditPatchPolicyComplianceWithReturn(token=token, device=device,

File "./urlopen.py", line 135, in getreply

 _blocking_read
communication time-out error: read timeout
A hotfix is available through HP Support.
QCCR1D179631 Patch Management Backend Linux, Solaris, AIX While patching approximately 100 Unix-based servers (Linux, Solaris and AIX), the environment becomes unresponsive and requires a restart. A hotfix is available through HP Support.

Patch Management UI

QCCR1D136931/137014 Patch Management UI Windows 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)
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.
QCCR1D148400/153334 Patch Management UI Windows 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. None.
QCCR1D176141 Patch Management UI Windows Exporting the patch compliance for a group of servers to a CSV file from SA Client takes a long time. None.

Server Automation Client

QCCR1D168719 SA Client Windows When you edit a package script, the user interface takes several seconds to display each keystroke. Edit the script in a notepad buffer and then copy/paste the entire buffer into the PackagePropertiesPanel.

Server Management (Backend)

QCCR1D179140 Server Management (Backend) Linux

Scheduling remediation jobs for a static device group of 240 servers fails, and the remediation job is not created.


The following error is visible in the twist.log:
#### <sho-p-hpsapp-01.company.com> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <[STUCK] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "719" seconds working on the request "com.opsware._gen.sejb.swmgmt.SoftwarePolicyService_hfpabb_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

Schedule a job for a smaller number of servers (less than 150).

Server Module (Backend)

QCCR1D156389 Server Module (SMO) Backend Windows 2012 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. None.

Software Management (Backend)

QCCR1D164397 Software Management Backend Independent RPM remediation fails if you update the SA Core to the latest SA version, but the associated satellite that the agent is connected to is an older version of SA. Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue.
QCCR1D177166 Software Management Backend Linux Preview mode can fail with Non-zero exit code (None) from dependency solve. None.
QCCR1D183132

Software Management

Independent

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

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

Virtualization - HP-UX

QCCR1D157368 HPUX Virtualization-HPVM Front End HPUX 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.  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.

Web Services Data Access Engine (Twist)

QCCR1D133589 Web Services Data Access Engine Red Hat Linux Web Services Data Access Engine takes too long to start up. None.
QCCR1D179479 Web Services Data Access Engine Independent The tokens used by recurring application configuration compliance jobs fail after a year because the tokens have a limited lifetime of one year. Recreate the job.

Additional Known Issues

The complete list of 9.1x known issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/documents
Note: This site requires that you sign in with your HP Passport and have an SAID. If you do not have authorization, contact your HP sales representative for details.

Search for Product: Server Automation, Version: 9.10, Document Types: Known problems.

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.

Fixed Issues

QCCR1D Symptom/Description Platform

AA

QCCR1D167959 /opt/opsware/twist/ldap_config.sh does not support multiple base DN searches. Linux
QCCR1D168463 WRITE_PERSISTENCE_ERROR messages in the twist logs, such as:
weblogic.ejb.OptimisticConcurrencyException: [EJB:010143]Optimistic concurrency violation. Instance of bean 'AaaUser' with primary key 'nnnnnnnn' was changed by another transaction.
 
... where 'nnnnnnnn' is a number.
Linux
QCCR1D171593 Access Engine process is interrupted at the HashMap.get() call.

Independent

Access Engine

QCCR1D165592 Inherited custom attribute access does not scale well. Independent
QCCR1D165724/166328 When audits are started manually, they do not run at the scheduled time, and the following error is displayed:

RemoteExeption occurred in server thread; nested exception is : java.rmi.RemoteException: EJB Exception:;nested Exception is : java.lang.NullpointerExeption'
Linux
QCCR1D167739 Audit execution fails with:

Failed:
Error Details:
HPSA-1800 : Source snapshot copy failed
An error occurred while copying the source snapshot from the source slice to another slice.
Independent
QCCR1D171685 The AWR report shows a very high number of buffer returns  from the ComplianceScanHelper.01 query. Linux
QCCR1D176240 Web Services Data Access Engine encounters socket timeouts and other timeouts.
Weblogic was upgraded to version 11g
Linux
QCCR1D176828/176835 Copy and Paste of OS Build Plans within HP SA Client Library does not copy custom attributes. Independent

Agent

QCCR1D169034 Agent migration fails due to 'port in use' error for HPSA agent ports. Windows
QCCR1D171798/171954 "Open with -> Remote PowerShell" on windows boxes will open a CMD shell instead of a PowerShell. Independent
QCCR1D174136 Default working directory for agent installation can be changed by using SA Client Device->Manage Server-> Advanced -> Extra installer options. Agent installation ignores the --workdir option set from SA client. Linux

Data Access Engine

QCCR1D166753 DCML Exchange Utility (DET) is generating the following error message when importing an HP-UX Product depot/package that is attached to a software policy.:
The object 'HPUXProductUnit' has no field named 'remove_flags'
Independent
QCCR1D169827 Using Repo.restrict custom attribute throws ORA-01795 when using a parent folder with more than 1000 sub-folders. Linux
QCCR1D175131 Software Registration errors with DBNotNullConstraintError on Windows server Windows

DCML Export Tool (DET)

QCCR1D168103 DCML Exchange Utility (DET) displays an import error when the target folder does not exist.
Missing folders now exist.
Linux

Global Filesystem

QCCR1D115140 Solaris OS experiences kernel panic and seizes to function. Solaris
QCCR1D168310 Audits fail and display the following error:
Error Details:
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: timestamp: 2013-06-17 18:52:19.6, messageKeyOrder: msg, msg: java.lang.NullPointerExceptionFound in: com.opsware.acm.way.SnapshotComplianceWayHandler ] was caught.

The error message appeared because the "0" directory was missing: /var/opt/opsware/word/mmword_local/audits/0/ on core server.  Directory is now created automatically.
Linux
QCCR1D171803 Remote terminal to Linux server does not create home folder on first time logon. Linux
QCCR1D176048/176051 SMO based audit throws "org.apache.noggit.NoggitException: invalid hex digit: char=\,position=1844" exception Linux

Installer

QCCR1D168038/168040 Too many world writable files under /opt/opsware. Independent

Jobs

QCCR1D170782/170785 Remediation jobs completed but missing details, some targets not acted upon Linux

OS Provisioning

QCCR1D176374 Reprovisioning jobs time out against any server with SAN attached  Independent

Patch Management

QCCR1D159560 Windows patching job failed on first MS patch with error code : 2147024770, 'The specified module could not be found' Independent
QCCR1D162682 Software Registration displays a DBNotNulConstraintError error. Windows 2003
QCCR1D174991 When you try to remediate a large number of servers, the remediate dialog box takes a long time to be displayed. Windows
QCCR1D175648 Windows Patching Remediation Scheduling for a group of servers times out. Linux

Software Management

QCCR1D165745 The custom attribute (CA) queries from opsware.swprov.doer should be disabled by default, instead of enabled by default (except for repo.restrict.<name>). Independent
QCCR1D167731 Require an efficient methodology to snapshot RHN channels.
Independent
QCCR1D168231 During an upgrade, when you remediate and install jobs on servers that contain OPSWpackage_path custom attributes (CA), you receive this error:
 
Start time:
-
End time:
-
Error Messages:
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
QCCR1D168451 Packages with response files fail to install. Solaris

Software Repository

QCCR1D158353 While running LNc import the following error is displayed:
OSError: [Errno 31] Too many links: '/var/opt/opsware/word/mmword_local/vcols/Unit/5953440001'
Linux

Additional Fixed Issues

The complete list of 9.1x fixed issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/documents
Note: This site requires that you sign in with your HP Passport and have an SAID. If you do not have authorization, contact your HP sales representative for details.

Search for Product: Server Automation, Version: 9.10, Document Types: Known problems.

Back to the table of contents




Deprecated Features

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

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

Deprecated API Methods

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

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

com.opsware.acm.ConfigurationService#create
com.opsware.acm.ConfigurationService#update
com.opsware.acm.CMLService#create
com.opsware.acm.CMLService#update
The following methods have been deprecated, but they still perform as expected. Method
com.opsware.folder.FolderVO#getCustomers should be used instead.
com.opsware.acm.ConfigurationVO#getCustomers
com.opsware.acm.CMLVO#getCustomers
The following methods have been deprecated and they have a void implementation. Method
com.opsware.folder.FolderVO#setCustomers must be used instead.
com.opsware.acm.ConfigurationVO#setCustomers
com.opsware.acm.CMLVO#setCustomers

Code Deployment and Rollback (CDR) and Configuration Tracking

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

If you upgrade to SA 9.16 and also upgrade to an SA 9.16 agent, you will no longer be able to use CDR because it is only supported if you are using SA 9.01 (or earlier) agents. However, you will be able to use CDR with SA 9.16 if you uninstall the SA 9.16 agent and reinstall an SA 9.01 (or earlier) agent (not recommended, as you will be unable to use other SA 9.16 features).

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

Agent Deprecation

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

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

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

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

DOS-Based OS Provisioning

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

start_opsware.sh and stop_opsware.sh scripts

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

start_opsware.sh
stop_opsware.sh

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

/etc/init.d/opsware-sas

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

Virtualization

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

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

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

The following Virtual Server reports were deprecated in 9.14:

Deprecated SMOs

The following SMOs were deprecated in 9.14:


Documentation Information

This section discusses documentation information for this release.

Documents Relevant to This Release

In addition to the SA 9.10 guides on the Self Solve website and the online help, the following white papers and guides are relevant to this release:

Documentation Errata

This section contains corrections for existing documentation.

SA 9.10 Administration Guide

SA 9.10 Standard/Advanced Installation Guide

SA 9.10 User Guide: Server Automation

Application Deployment Manager Context-Sensitive (F1) Help

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

To view a context-sensitive help topic, click the question mark icon in the dialog.

Note: The F1 key does not open online help for the Application Deployment Manager.

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

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


SA 9.10 Integration Guide

On page 25, Network Reports section, disregard the following reports:

The only reports available in SA are "Connections by Network Device" and "Connections by Server".


SA 9.10 Simple/Advanced Installation Guide

SA 9.10 User Guide: Application Configuration

SA 9.10 User Guide: OS Provisioning


SA 9.10 User Guide: Server Patching

In chapter 4:

SA 9.10 User Guide: Server Automation

SA 9.10 User Guide: OS Provisioning: Support for Linux PowerPC 64-based Network Booting

From an Open Firmware prompt, enter:

0 > boot net:,yaboot,,

This retrieves the yaboot boot loader and the boot menu is displayed:

"Choose a boot image by entering the appropriate label at the 'boot:' prompt.

linux5    - Linux Build Agent (RHEL 5.8-based)
linux6    - Linux Build Agent (RHEL 6.3-based)

Welcome to yaboot version 1.3.17
Enter "help" to get some basic usage information
boot:"

Support Matrix

Please note the following documentation errors:

Documentation Additions

This section contains additions to existing documentation.

SA 9.10 Simple/Advanced Installation Guide

SA 9.10 Administration Guide

SA 9.10 User Guide: OS Provisioning

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-2014 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
March 26, 2014 Added errata in the Administration Guide re: audit trails.
May 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