Original Publication Date: July 19, 2013
Server Automation (SA) is the Enterprise Edition of Server Automation. For information about Server Automation, see the SA Release Notes and the SA User Guide: Server Automation.
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 9.15 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.
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.
This document contains the following information:
New Features in This Release |
Installation |
Known Issues |
Fixed Issues |
Deprecated Features |
Documentation Information |
HP Software Support |
Legal Notices |
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.
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.
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 |
This section lists the operating-systems supported on the SA Client.
Make sure you follow these steps before you install SA:
Note: These new drivers might introduce issues for legacy hardware that uses those drivers. See the following article for potential solutions, or contact HP Support:
This section describes the installation procedure.
patch_opsware.sh
script is used
both for installing and for uninstalling SA 9.15. patch_opsware.sh
. patch_database.sh
script is used both for installing and rolling back database schema
changes required for SA 9.15. patch_database.sh
script on the First Core and all Secondary Cores. Note that the
Model Repository and Oracle database can exist on a different host than the SA
host. patch_database.sh
. If any installed SA components (other than a previously installed patch) have a different build ID, you will not be allowed to install SA 9.15.
/var/opt/opsware/install_opsware/inv/install.inv
and find the section beginning with
%basics_
. Under this line, find thebuild_id
.
For example:
%basics_linux
build_id: opsware_45.0.6790.0
When you install an SA patch, the patch installation updates the
install.inv
file to record the patch installation and the patch build ID.For example:
%opsware_patch
build_id: opsware_45.0.17090.0
/etc/init.d/opsware-sas status
command), the patch operation will terminate. If you must roll back the SA 9.15 patch in a Multi-master Mesh, HP recommends that you roll back the secondary cores and satellites first, then the primary core.
spog.pkcs8
certificate must exist under /var/opt/opsware/crypto
(typically the
certificate is installed with the Shell, SAS Web Client, or Build
Manager). If the certificate does not exist, the patch operation will fail
with the following error:
Could not find spog.pkcs8
/var/opt/opsware/crypto/occ
Copy the certificate from another core machine
(for example, occ ) to
/var/opt/opsware/crypto/occ
and
retry this operation.
If this error is encountered, simply copy the certificate from another core machine to your core server and retry the operation.
/var/opt/opsware/crypto/spin
(typically the
certificate is installed with the Web Services Data Access Engine ( spin )). If the certificate does not exist, the patch
operation will fail with the following error:
Could not find spin.srv under
/var/opt/opsware/crypto/spin.
Copy the certificate from another core machine (such as occ) to
/var/opt/opsware/crypto/spin
and retry this operation.
You don't have permission to update the patch meta
database in HP SA.
Please re-run this command with a proper hpsa_user and
hpsa_pass.
The hpsa_user needs permission to write the folder
"/Opsware/Tools/Solaris Patching" and the Package Management
Client
Feature, "Manage Package" permission set "Read & Write".
There was a
problem with running update_supplements.
Please refer to section Patch
Management for Solaris of the Users Guide:
Application Automation manual
for details on how to set up Solaris
patching on your core.
You can safely disregard this error.
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 |
|
SA Script Running Order - Rollback
Roll back From |
To |
Script Running Order |
---|---|---|
9.15 |
9.10 |
|
When migrating from SA 7.8 to SA 9.1x:
When migrating from SA 9.0 to SA 9.1x:
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:
The error message should not display.
The script run during this procedure makes required changes to the Model Repository including adding required tables and objects.
patch_database.sh
on the Model Repository
host:
<distro>/opsware_installer/patch_database.sh --verbose -r <response file>
Where <
response file
> is the response file last used to install/upgrade the system.Usage:
patch_database.sh
[--
verbose
] -r <response file
>
patch_database.sh
automatically detects if a database update is already installed and presents a corresponding menu:
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
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.
[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.
All SA installation DVDs require a DVD drive that supports dual layer.
Perform the following tasks to install SA 9.15:
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:
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.
patch_opsware.sh
is invoked from a newer patch 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.
The installer displays the following upon completion:
[<timestamp>] Done with component Opsware
Patch.
[<timestamp>]
########################################################
[<timestamp>] Opsware Installer ran
successfully.
[<timestamp>]
########################################################
This section details upgrades to the software repository content on the upload distribution (such as agent packages to be reconciled to managed servers).
patch_opsware.sh
from the upload
distribution, but will only update those packages that have changed since
the last major version. word
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.
[<timestamp>] There are no components to
upgrade.
[<timestamp>] Exiting Opsware Installer.
To roll back SA 9.15 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.
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/.
<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.
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/.
This section lists the tasks that should be performed after you install SA 9.15. Some tasks might not be appropriate for your situation.
If SA 9.15 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 9.15 install or upgrade:
Directive:
opswgw.SoReuseAddr=false
Redhat has a description of this issue on their website: https://access.redhat.com/site/solutions/357683
If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after upgrading to SA 9.15, 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.
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:
cd
/var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts
Command #2:
./post_after_startup.sh
If you have customized such settings as Java heap settings, you must reapply your customizations after you install 9.15, as the settings are set to the SA default during installation or upgrade.
Since 9.11, SA Agents have used Python 2.4.4.
After you upgrade to SA 9.15, you should also upgrade to the 9.15 SA Agents on each Managed Server in the facility. If you do not upgrade your agents, the new functionality will not be available.
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:
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
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)
This section describes issues from SA versions 9.0, 9.01, 9.02, 9.03, 9.10, 9.11, 9.12, 9.13, 9.14, and 9.15. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.
Known Issues
QCCR1D | Symptom/Description | Platform | Subsystem | Workaround |
---|---|---|---|---|
AAA | ||||
QCCR1D165502*** | If SA is using LDAP to authenticate off an Active Directory (AD) domain, it uses the DN as the identifying factor. If the DN changes in any way, that user can no longer login.
To resolve this, you have to delete, and then recreate, the user. The user's private device groups are deleted. |
Independent | AAA | Contact HP Support for information on a 9.15 hot fix that addresses this issue. |
QCCR1D167959*** | /opt/opsware/twist/ldap_config.sh does not support multiple base DN searches. | Independent | AAA | Contact HP Support for information on a 9.15 hot fix that addresses this issue. |
Administration UI |
||||
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. |
Agent |
||||
QCCR1D100660 | Windows ADT login fails for administrators that are not user Administrator due to security controls for Windows UAC. | Windows Server 2008 using UAC | Agent Deployment | Turn off UAC:
|
QCCR1D107917 | Failed SA agent installation returns gencache.py
error message in the agent log file
(%SystemDrive%\Windows\System32\opsware-agent-installer-
|
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 %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. |
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. |
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. |
QCCR1D167887*** | Software policy remediation of multiple packages with reboot option fails at install stage with batchbot error:
The operation to install or uninstall software failed. |
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 9.15 rollup 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):
|
QCCR1D161564*** | Recurring Scheduled Extensible Discovery Job does not update servers.
Customer noticed that new servers that are added to the dynamic group, are not being included in the Extensible discovery job. |
Independent | A[X Framework | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
Audit and Compliance |
||||
QCCR1D135276*** | When you open a managed server and browse the filesystem, SA allows you to select one or more files to add to the SA Library. The selected files are added to a specified folder in the SA Library. However, in HP-UX, if you select more than one file to add to the library, you get an error similar to the following:
OpswareError: collectionObjectCreation.MissingPermissions [ module: com.opsware.compliance.server.rmi, method: createPackage, line: 188, timestamp: 2011-05-12 14:10:38.324, msg: java.io.IOException: Error creating file system ZIP archive. message: HP-ROMAN8; cause: null, stacktrace: java.io.IOException: Error creating file system ZIP archive. message: HP-ROMAN8; cause: null |
HP-UX | Audit and Compliance | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
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:
|
Independent | Audit and Compliance | Update any audit or snapshot with a rule that depends on any of these fields:
|
QCCR1D168072*** | Audit job reports an out-of-compliance status although the expected value in the registry key is correct. | Independent | Audit and Compliance | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
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:
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. |
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. |
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. |
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:
|
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:
Procedure 2: Complete Install:
|
Device Groups (Backend) |
||||
QCCR1D168478*** | Recalc cannot be disabled without disabling the Web Services Data Access Engine. | Independent | Device Groups (Backend) | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
Gateway |
||||
QCCR1D165971 | Sporadic org.omg.CORBA.COMM_FAILURE exception is displayed in the SA Client console. | Red Hat Linux 5.9 | Gateway | To work around this issue:
Redhat has a description of this issue on their website: https://access.redhat.com/site/solutions/357683 |
Global File System |
||||
QCCR1D167608*** | Failures running OGSH commands in SA from OO. | Independent | OGFS | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D168562*** | The Network Access Service (NAS) interface links are broken in the OGFS. | Independent | OGFS | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
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 to version 9.1X, wayscript versions are set to version 9.10 rather than to the patch version. | Independent | SA Installer | In the SA Web Client:
|
QCCR1D132004 | Health check fails with mismatched core component version errors (check_occ_up, lnxisoupload, new_platforms, opswbia_upload). | Linux | 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. |
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. |
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:
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 |
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 |
To work around this issue:
|
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:
|
Independent | OS Provisioning - Backend | Manually set the RAID controller configuration:
After the RAID controller has been manually configured, |
QCCR1D104739 | During a network boot of the server, the following error displays: "No driver found" screen appears: " |
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. |
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"> |
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. |
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 reprovisioned 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:
|
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 |
QCCR1D146347 |
Linux 6-OGFS boot failed on HP ProLiant DL380 G4 and DL385 G1. | Linux | OS Provisioning | None. |
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. |
QCCR1D147226 | An iLO's realm information is not updated after the iLO is moved from one satellite to another. | Independent | OS Provisioning | Remove the iLO server, then add it again, this time into the correct realm. |
QCCR1D156536 | DHCP-less provisioning fails for Windows Server 2012 Essentials. | Windows | OS Provisioning Backend | None. |
QCCR1D159441*** | RHEL/SLES builds are failing with the following error: RHEL : Agent installation failed with return code of: 1024 |
Linux | OS Provisioning Backend | Contact HP Support for information on a 9.15 hot fix that addresses this issue. |
QCCR1D168351*** | If the server has a system time that is older than the SA custom-attribute's beginning time on the SA Core, the OGFS agent will fail to download packages from the core during provisioning. | Independent | OS Provisioning | Unix only (does not work for other OSs): Add a build step that modifies the hardware clock. |
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) |
||||
QCCR1D168655 | 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 for HP-UX |
||||
QCCR1D157372 | SA displays an incorrect message when it tries to remediate an HP-UX server if the following conditions are present:
|
HP-UX | Patch Management | None. |
Patch Management for Linux |
||||
QCCR1D167036 | Automatically installing ControlM package on managed hosts does not work with Yum version 3.2.22, because this version of Yum does not support the nodeps option. | Linux | Patch Management | Download the ControlM package and install it manually, using the same options that are used for automatic configuration. |
Patch Management for Solaris | ||||
QCCR1D100566 | Although the reboot is performed correctly, when you preview remediating a patch policy on a server, or view the job status for a patch policy that is already remediated, the reboot setting might incorrectly display “Install and Reboot Later” when it should display “Install and Reboot”. | Solaris | Patch Management - Solaris | A workaround is not required because the reboot is performed
correctly, even though the display may be incorrect. |
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 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:
After you have installed SA, perform
these tasks to recreate
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:
|
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, you must manually run update_supplements to see new clusters, such as Fujitsu clusters. | Solaris | Patch Management - Solaris | SA 9.10 provides 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 or SA 9.15), where the mesh has Solaris patching configured (solpatchdb). After the mesh has been upgraded to SA 9.15, 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 |
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:
|
QCCR1D152933 | 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: |
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. |
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:
“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. |
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: |
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. |
QCCR1D149171/144269 | When SA installs any patch policy containing KB921896 SP2 for SQL server 2005, SA inaccurately reports the patch policy as non-compliant. . |
Windows | Patch Management - Windows - Backend | Install one of the following KBs instead of KB921896: KB955706 (SP3) or KB2463332 (SP4). |
QCCR1D150358 | Remediation fails for XenServer 6.0.2. with the following error: "The request to retrieve information from the Agent failed for an unknown reason, please contact your HP Server Automation Administrator.Execution error: Traceback (most recent call last): File "./base/wayfuncs.py", line 136, in evaluator File " ", line 2303, in ? File " ", line 2228, in main File " ", line 1360, in doYumAnalyze OpswareError: args: () been_cascaded: 0 error_id: None error_name: cogbot.reconcileFailed faultCode: 101 faultString: cogbot.reconcileFailed hostname: dhcp-163-56.copper.qa.opsware.com line: 1360 method: doYumAnalyze module: params: {'messages': 'Failed to setup RPM database:\nerror: creating directory /var/opt/opsware/yum/run/rpmtmp/rebuild: Permission denied\n'} request: UNKNOWN tb_chain: [] timestamp: 26/Jun/2012 104732 timeticks: 1340707652" Remediation fails for Xen6.02 with the following error: "The request to retrieve information from the Agent failed for an unknown reason, please contact your HP Server Automation Administrator..." |
Windows | Patch Management - Windows - Backend | To perform Software Management functions on a XenServer 6.0.2 machine, run the following script to grant the necessary permissions on the "/" folder: chmod 755/ |
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 | After a Windows Patch Metadata (MBSA) import is complete, it takes longer to update patches in the library and database information section of the Administration page because the import operation exceeded the import timeout default of 60 minutes. | Windows | Patch Management - Windows - Backend | None. |
QCCR1D153334 | 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 | None. |
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: 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. |
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. |
QCCR1D164689*** | Option Suppress all server reboots is not properly set in install software jobs. | Windows | SA Client Framework | Contact HP Support for information on a 9.15 hot fix that addresses this issue. |
QCCR1D165483*** | If you create an advanced search of servers and receive a large result set, then sort on the custom-field column, you might see an out of memory exception (OOME) error. | Windows | SA Client Framework | Contact HP Support for information on a 9.15 hot fix that addresses this issue. |
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/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. |
Script Execution | ||||
QCCR1D79545 | Exporting a Run Server Script Job output containing multi-byte
characters (Japanese/Korean) to .csv results in question
marks in place of the multi-byte characters. |
Windows | Script Execution | Export the job results in .txt format to eliminate the
garbled text. |
SE Connector | ||||
QCCR1D88755 | There is no Target and Target Volume information displayed in the storage volume access path view for a LUN. | Independent | SE Connector | None. |
QCCR1D91582 | When you perform a provisioning operation for an HP EVA array (such as create, delete, or modify a volume or pool), the changes for the volume or pool might not be immediately available in the corresponding Inventory view in SA after running the "Update from Storage Essentials" process. | Independent | SE Connector | After 30 minutes has lapsed, run the "Update from Storage Essentials" process again. See the Storage Essentials SRM Software User Guide for information about provisioning EVA arrays. |
QCCR1D105778 | When a server on which SE Connector is running is directly
deactivated and deleted, selecting Administration -> Storage
Scanners -> <The names of the SE Scanner on "Host">
shows stale entries of Storage scanners in the Scanner
panel. The stale entries count will increase, depending on how many
times the server is deactivated and deleted from the core. |
Independent | SE Connector | Manually delete the inactive Storage Scanner entries from the Storage Scanner panel by using the Remove menu option provided for each entry. |
Server 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. |
QCCR1D163940 | 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. |
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. |
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. |
QCCR1D164397*** | 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. | Independent | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D164878*** | SA GUI does not correctly display remediation jobs created using the pytwist script. | Independent | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
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 | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D167731*** | Require an efficient methodology to snapshot Red Hat Network (RHN) channels. | Linux | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D168231*** | Regression with OPSWpackage_path custome attributes (CA) in stage_blob when peer cache functionality was added.
When you upgrade to 9.15, and try to remediate and perform software installation jobs on servers that contain OPSWpackage_path custome attributes (CA), you receive this error: Start time: |
Independent | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D168451*** | Solaris packages with response files fail to install/uninstall. The following error is displayed:
The operation to install or uninstall software failed. |
Solaris | Software Management | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
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:
|
Independent | Software Management | Follow the steps explained in the Server Automation Alert: Remediation Job Loss During Upgrade/Rollback SRVA 00176 |
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. |
Storage Host Agent Extension | ||||
QCCR1D93630 | LUNs that are multipathed by EMC PowerPath are shown as both "ROOT" and "LUN" in the Inventory -> Storage -> Volumes Panel alongside LUNs that are correctly displayed. The SCSI Bus number provided by PowerPath (using the powermt command) does not match the bus number of the disks (LUNs). | Windows | Storage Host Agent Extension | None. |
QCCR1D93690 | The Server -> Relationships -> SAN
Switches panel on a virtual server is empty/only displays SAN switches to which the given server is directly connected. In some cases, a server may depend on SAN switches that are not displayed in this panel. For example, a virtual server may be using storage allocated from a hypervisor that was allocated storage from a SAN. |
Independent | Database Scanner for Oracle | None. |
QCCR1D105382 | When you run the storage snapshot specification, the disk capacity
information is changed in the Inventory -> Storage -> Disk panel. This occurs if there is a mismatch in the disk names, as reported by the hardware registration script and the storage snapshot specification. |
Windows 2008 | Storage Host Agent Extension | Reboot the server after changing disk information (such as
installing or uninstalling multipathing software, presenting new LUNs,
deleting LUNs, and so on), and run the hardware registration before running the storage snapshot specification. |
QCCR1D105953 | An EMC Symmetrix array that is discovered through SE Connector can report more than one storage volume with the same LUN number presented to a managed server. Running the storage snapshot specification on the managed server will succeed; however, the Inventory -> Storage -> File Systems and Inventory -> Storage -> Managed Software panels will be empty. In addition, some host volumes with a LUN service type will not be displayed in the Storage -> Inventory -> Volumes panel. | Independent | Storage Host Agent Extension | None. |
QCCR1D106400 | The right-hand panel under Inventory -> Storage -> Volumes does not display the supply chain and composition information
properly (or the information is missing altogether) for some volumes that were created out of LUNs |
AIX | Storage Host Agent Extension | Delete the stale volumes on the AIX managed server and run the storage inventory snapshot specification. |
QCCR1D106699 | For managed servers with mirrored volumes, if one of the disks that
is part of a mirrored volume fails or is removed, the state of the
volume is shown as "Failed Redundancy" in the Disks Management panel. However, in the Inventory -> Storage -> Volumes panel for the managed server, the status of this volume is shown as "OK", even after running storage snapshot specifications. |
Windows 2008 | Storage Host Agent Extension | None. |
QCCR1D107944 | Running a storage snapshot specification on unsupported ESX 3.0.x servers returns an error message that indicates unsupported namespace in content of SOAP body. Storage related information for ESX 3.0.x is not stored and displayed in the SA Client. | VMware ESX 3.0.x | Storage Host Agent Extension | None. |
QCCR1D111724 /111727 |
Host Storage Inventory does not support VMware servers that have VMDK on NFS datastore. Therefore, no storage information will be collected on VMWare servers with this configuration. |
All VMware servers | Storage Host Agent Extension | None. |
Bug ID: 149406 / 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 nodein 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:
|
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 |
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 arereturned, 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 theSTORAGE_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. |
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. |
QCCR1D157571 | When you choose a server, then right click the server and choose Open With > UCMDB browser, it opens a blank web page. | Independent | UCMDB | Make sure that the UCMDB server is configured and that the Tellconnector is running.
If the server is configured and Tellconnector is running, contact your system administrator. |
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:
When migrating from SA 9.0 to SA 9.1x:
|
Virtualization | ||||
QCCR1D90019 | If a system has more than one virtual network with the same name, even if those networks are managed by different hypervisors, scanning for virtual servers fails due to a violation of unique name constraints. | Windows Server 2008/Hyper-V | Virtualization | Do not use duplicate virtual network names. |
QCCR1D104418 | The reported OS property text for ESX servers is inconsistent between direct (SA Agent) and indirect managed (vCenter) cases. | VMware ESX (all versions) | Virtualization - Backend (VMware) | None. |
QCCR1D105999 | After cloning an SA-managed virtual machine, when the new clone starts
up for the first time but cannot obtain network connectivity, agent
revival will fail to create a new server record for the new clone. |
Independent | Virtualization - Backend (VMWare) | Restart the agent on the new clone after network issues are resolved and the agent will correctly register as an SA-managed virtual machine. |
QCCR1D106085 | If your Hyper-V server has more than one IP address, SA might change the Management IP address from the one you registered to one of the other IP addresses. | Windows Server 2008 pre-R2 server | Virtualization - Hyper-V | To prevent this problem, you need to manage your Windows 2008
pre-R2 server from a Windows 2008 R2 server and make sure the option to
allow the management operating system to share the network adapter
is not selected. The following gives the basic steps to accomplish
this, however, see your Microsoft Hyper-V documentation for complete
details. More information may also be available by searching the
internet for "New in Hyper-V Windows Server 2008 R2" and "Hyper-V
Remote Management: You do not have the required privileges to complete
this task."
|
QCCR1D106909 | Clone Virtual Machine job will fail the Registering Server step if the Windows Shutdown Event Tracker is enabled on the source virtual machine. This is because the Shutdown Event Tracker waits for user input before it completes rebooting, so the SA Agent registration cannot complete. | Windows | Virtualization | Disable the Shutdown Event Tracker on the clone source virtual server. Windows 2003 x64 cloning requires a manual reset to resume virtual machine images customization. |
QCCR1D109887 | The snapshot view is not available on an ESX server that is managed by vCenter. |
Red Hat Linux | Virtualization | Manage ESX directly snapshot view. |
QCCR1D110035 | When a hypervisor that is dual-managed (through Virtualization Service and SA Agent) loses one of its management paths (such as when the Virtualization Manager or VCenter is removed from SA) the Login Credentials panel does not display in the server browser panel and the hypervisor credentials do not display in the Properties view. | VMWare ESXi | Virtualization | Right-click on the hypervisor, select "Refresh Server", and then press F5 (Refresh) to refresh the client so that the Login Credentials panel displays in the server browser. |
QCCR1D111307 | If you add an ESXi server with larger hardware configuration data, the add operation suspends processing. | ESXi | Virtualization - Backend (VMWare) | Reconfigure the server with fewer CPU counts in hardware information. |
QCCR1D111780 | Hypervisors are not loading. | Windows | Virtual Center | Check that the hypervisor version you are using is supported. Or
check to see if the hypervisor is in a NOT RESPONDING
state. |
QCCR1D111789 | Adding two vCenters concurrently results in one of the automatically triggered reload data to suspend processing. | Independent | Virtualization - Backend (VMWare) | Add the vCenters separately. |
QCCR1D111922 | The Create Virtual Machine operation on an SA managed ESX 3.5
server fails with an error message of
com.vmware.vim25.VirtualMachineConfigSpec. |
ESX 3.5 | Virtualization - Backend (VMWare) |
After the SA 7.5 release, one of the VMM library jar files was
changed from OPSWvmm-vmware.jar to vmm-vmware.jar. When an
upgrade is performed from SA 7.5 directly to SA 9.0, or from SA 7.5 to
SA 7.8 to SA 9.0, and any virtualization operation is invoked on the
ESX hypervisors, the VMM package gets remediated first with the new package but the OPSWvmm-vmware.jar file is left
untouched. This causes the consecutive virtual machine create operations to fail. The following workaround is intended for any ESX
hypervisor that is managed by an Agent in SA and whose
virtualization aspect will still be handled through the same route (not
via VS)
|
QCCR1D111972 | Create Virtual Machine fails on a directly managed ESX hypervisor if the virtual machine's datastore name contains special characters. | ESX | Virtualization - Backend (VMWare) | Change the datastore name so that it does not contain special characters. |
QCCR1D116276 | After an SA Agent is installed and before hardware registration has completed, you can create or modify a virtual machine with a memory value that is larger than the hypervisor's physical memory. The job completes successfully. | Windows 2008, Windows 2008 R2 | Virtualization - Hyper-V |
Run a full hardware registration on the Windows server. After hardware registration is completed, SA will not allow you to use memory that is greater than the maximum memory allowed on a virtual machine for the actions to create and modify a virtual machine. |
QCCR1D146111 | Permission denied to run APX v12n.apx.utility when you try to add an ESXi hypervisor. | ESX | Virtualization - Backend (VMWare) | In order to add an ESXi hypervisor (or to run ESXi5 Build Plan OS Provision) you must also have Allow Install Agent (SA Client) or Allow Managed Server (SA Web Client) action permission. |
QCCR1D157237 | Error in java console when calling the VirtualServerService.getAllVirtualServerRef function. | ESX and ESXi | Virtualization | None. Functionality is not affected. |
QCCR1D155889 | Add Hypervisor can fail when the hypervisor has certain hardware configurations. | ESXi 5.1 | Virtualization | If Add Hypervisor hangs, whether invoked as part of an OSBP, or directly, ensure the hypervisor has all its NICs connected and try again. |
QCCR1D157368 | 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. |
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:
|
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 |
QCCR1D163506*** | Whenever the NAMESPACE_LUS table is joined in the following SQL queries, it results in a Cartesian join and a sub optimal execution path:
twist/twist/applications/swmgmt/session/src/com/opsware/pkg/impl/PatchImplHelper.java |
Independent | Web Services Data Access Engine (twist) | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D167739*** | Audit execution fails with the following error:
Failed: Contact your system administrator and check to see if an opsware agent is running on the source slice. |
Independent | Web Services Data Access Engine (twist) | Contact HP Support for information on a 9.15 rollup hot fix that addresses this issue. |
QCCR1D168519*** | LRUCache WaySessionUtils.srcache can cache empty results. | Independent | Web Services Data Access Engine (twist) | Contact HP Support for information on a 9.15 rollup 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: |
*** Known issues denoted with three asterisks (***) might have a Hot Fix available, but the fix was not included with SA 9.15. An updated rollup Hot Fix for 9.15 is planned. Contact HP Support for more information.
Back to the Table of Contents
The Fixed Issues table includes issues that:
The table lists issues first by subsystem, then numerically within each subsystem.
QCCR1D | Symptom/Description | Platform |
---|---|---|
AA |
||
QCCR1D157880 | A device group is still treated as access group after the user group that had it as control boundary was deleted. | Independent |
Agent |
||
QCCR1D158717 | Batch bot terminates the Install Script after one hour. | Linux |
QCCR1D159814 | Remediation of certain RPM packages can get stuck if the RPM package starts up services. | Independent |
QCCR1D160363 | HP-UX agent can return wrong serial number. | HP-UX |
QCCR1D160578 | 'Run Server Script' not respecting secondary groups. | Independent |
QCCR1D161510 | Win OS Sequences fail with "Error 10051 while connecting to xx:3001". | Independent |
QCCR1D161685 | x86 Solaris agent serial number detection improvement. | Solaris |
QCCR1D162971 | Detect_hardware on Linux cannot detect em* or p* interfaces on RHEL6. | Linux |
QCCR1D164029 | set_customer.sh tool gives error: Found more than one customer with name EIS-UTE. | Independent |
QCCR1D164613 | Unable to run server scripts when tmp is set to noexec. | Independent |
QCCR1D158571 | winpe64 no longer works with 9.1x in ESX 4.1U3 guest. | Independent |
QCCR1D160805 | The following error message is received when installing an SA agent on a Windows 2008 server:
Service_Control_Manager - event ID 7030 - description: |
Independent |
APX |
||
QCCR1D160329 | Differences in opsware.passwd_change.win32_blob between SA 9.05 and SA 9.1x. | Independent |
QCCR1D161405 | apachemonitor.py goes into an infinite loop on external socket close. | Independent |
Application Deployment Manager |
||
QCCR1D133132 | The Application Deployment Manager now installs correctly on an Oracle RAC instance, regardless of the Oracle TNS entry line format. | Independent |
QCCR1D138678 | Target groups are now consistently displayed properly in the Application Deployment Manager. | Independent |
QCCR1D142009 | The following special variables are now available: Server IP Address, Deploy Server IP Addresses, and Server IP Addresses for Tier <name of the tier>. | Independent |
QCCR1D142223 | You can now specify a Base Directory for Configuration File type components and Code type components. | Independent |
QCCR1D142852 | The Manage Applications dialog will now allow you to select only one application at a time. | Independent |
QCCR1D158723 | The Application Deployment Manager no longer reports an error when a user who has the required permissions changes the status of an environment within a lifecycle. | Independent |
Audit and Compliance |
||
QCCR1D150583 | After upgrading, audit-result emails are now empty for successful results | Independent |
QCCR1D152831 | Audit Result Exports in SA Client take 4X longer than they did in SA 9.0. | Independent |
QCCR1D159358 | ttlg/rosh handshake timeout can occur for large saved scripts over slow networks. | Independent |
QCCR1D160642 | Construction of large audits can cause the session token to expire (after 30 minutes). | Independent |
QCCR1D157460 | Audit added to Dynamic Device Group is not displayed in the individual server's pane. | Independent |
Audit and Remediation |
||
QCCR1D144852 | Until restart, cannot run audit jobs. | Independent |
QCCR1D156698 | Compliance view does not show status for the Audit policy when snapshot of snapshot spec with linked audit policy is source of an audit. | Independent |
BSAE Integration |
||
QCCR1D158187 | Generate reports that use fields in SA. | Independent |
Command Engine |
||
QCCR1D145465 | Requesting wayscript configurable timeout for ssct_run. | Independent |
QCCR1D156799 | svc_service_list.sh does not handle carriage returns correctly. | Independent |
QCCR1D160398 | A BLOCKED scheduled session started once the user was unsuspended. | Independent |
QCCR1D160610 | During a large remediation job, various data structures that are passed down to the doer subsession become very large (around 100 MB). This causes a breach of the hard-code, 60-second read timeout associated with the proxyCommand method that the XMLRPC client invokes. | Independent |
Compliance Dashboard UI |
||
QCCR1D164840 | Compliance scans for software policies comprised completely of packages in other software policies attached to the server return message "Note: No Rules Associated with Policy" |
Independent |
Data Access Engine |
||
QCCR1D156002 | Agent certificate generator is not running due to empty ca.db.serial file. | Independent |
QCCR1D159827 | Gross inefficiency in Data Access Engine string-chunking algorithm. (ChunkedChildrenObject.setText) | Independent |
QCCR1D162246 | The default values of alertAddresses and alertFrom are set to None, causing ./init/cronbot_init.py to fail with a System Diagnostic error, and impeding set up of cronbot jobs. | Independent |
QCCR1D165757 | Allow some custom attributes to be disabled on the Data Access Engine to increase throughput at the expense of reduced functionality (redux). | Independent |
DCML Export Tool (DET) |
||
QCCR1D167377 | CBT checksum algorithm is slow and uses a large amount of memory. | Independent |
Device Groups |
||
QCCR1D159365 | The _localDeviceSet/Recalc.20 query is not correct. | Independent |
QCCR1D164676 | Device Groups cannot parse with comma. | Independent |
Gateway |
||
QCCR1D166041 | Several mesh-wide outages were caused by opswgw tunnel disruption that can lead to stuck proxied TCP flow. Allow this setting to be customer configurable.
The value of the Web Services Data Access Engine transaction (pre-twist fix) default value was reset from 20 to 30 minutes. |
Independent |
Global Filesystem |
||
QCCR1D145173 | findObjRefs does not work for searchableType='user". | Windows |
QCCR1D162217 | Supply a list of Global Shell commands and how to use them.
The --help option was added to the API methods.. For example: Prints the usage: |
Windows |
QCCR1D164325 | Request: List of Global shell commands to access HP SA and how to use them. | Windows |
Installer |
||
QCCR1D159460 | After OI completes the deployment of the CORD patch, the /etc/sysctl.conf is absent. |
Independent |
Jobs Backend |
||
QCCR1D154565 | SA Client takes long to load "Run Server Script" job results. | Independent |
QCCR1D163334 | Unnecessary calls to the authorization service causing delays and preventing the job from starting when remediating more than 100 servers. | Independent |
QCCR1D164848 | Better error handling and messaging for Remediation proxy timeout errors. | Independent |
QCCR1D165832 | OGFS Script failure with the following error: Missing fields ([token]) + Error from remote (1691). | Independent |
OS Provisioning - Backend |
||
QCCR1D158865 | MBC uses a registered software query instead of RC attachment to find the Opsware DHCP servers | Independent |
QCCR1D161896 | OS Provisioning of RedHat systems will fail if SELINUX is enabled | Linux |
OS Provisioning - UI |
||
QCCR1D159412 | DHCP MBC Cleanup form broken. | Independent |
QCCR1D164328 | Unable to run OS build plan when user was created with a ":" char on the full name. | Independent |
Patch Management - Backend | ||
QCCR1D155791 | Handle the CopyToCache exception for patch to allow the rest of the patches to be installed. | Independent |
QCCR1D159430 | Windows patch remediation takes long time after upgrading to 9.1x. | Windows |
QCCR1D160822 | RHN import failing with the following unexpected error: KeyError: 'channel_name'. | Linux |
QCCR1D166319 | Importing a depot file without machine_type set in the catalog/INDEX file results in an "Invalid depot file" error. | Independent |
PowerShell Integration |
||
QCCR1D161368 | Powers hell custom script in Audit is compliant even if the script itself fails. | Independent |
QCCR1D161369 | If you install the new agent for Windows 2012, you cannot run PowerShell v3 scripts. | Windows 2012 |
SA Client (Framework) |
||
QCCR1D115211 | Launching the SA Client under Windows Vista or Windows 7 causes flickering/redrawing of the screen. | Windows Vista, Windows 7 |
QCCR1D115403 | The SA Client freezes when any of the following items is launched for the first time: Application Deployment, Web Automation Platform Extension (APX) processes (including OS Build Plans and HP Virtualization), and reports. | Windows |
SA Client (Network) |
||
QCCR1D157210 | SA Client freezes because of long running tasks on the awt event-dispatching thread. | Independent |
QCCR1D167688 | Getting an internal error with a null pointer exception when trying to view a one-time scheduled job in the future. | Independent |
Scripts Backend |
||
QCCR1D156243 | Server scripts failing with the following Error Code: wayscripts.lockFailed. | Independent |
QCCR1D157583 | Failed result by POKEFAIL does not show in the SA Client's Job Progress window. | Windows |
Search Backend |
||
QCCR1D158498/158492 | Inherited custom attributes without value cannot be used in searches. This causes all searches based on inherited custom attributes (including existing device group recalculation rules that are based on CA keys without a defined value) to return no results. | Independent |
Server Management - Backend |
||
QCCR1D158040 | Core recertification failure during phase 7 due to space in realm name. | Independent |
QCCR1D162078 | When you boot up your HP DL380 G6 server with the SA boot ISO and attempt to provision Linux 5.6, the OS installation is successful, but the agent is never installed after the final reboot. This results in the following timeout error in the build manager logs:
*********** BuildscriptError ************ |
Linux |
Server Management - UI |
||
QCCR1D158686 | SA Client remote terminal via Remote Desktop (RDP) fails for Windows 2003. | Windows 2003 |
Software Management |
||
QCCR1D143574 | Unable to attach a server to a software policy without immediate remediation. | Independent |
QCCR1D159357 | SA hangs when installing certain Linux packages with pre/post install scripts. | Linux |
QCCR1D159481 | opsware.swprov.doer semaphore experiences over-release and deadlock. | Independent |
QCCR1D159574 | zip_handler is incorrectly using statvfs.F_BSIZE in calculations for available space. | Independent |
QCCR1D159619 | The following error is occasionally seen when processing jobs: "KeyError: 'special_reboot_dict'". | Independent |
QCCR1D160776 | Unable to add items to a policy with read-only permissions on a library folder. | Independent |
QCCR1D160863 | Unnecessary parameters passed to child doer from chunker during remediation. | Independent |
QCCR1D162181 | Solaris 11 recommended patch policy is not created when using solpatch_import. | Solaris |
QCCR1D165183 | Remediation data structures contain too much redundant information and do not scale well. | Independent |
Software Management UI |
||
QCCR1D158583 | Unable to attach software policies to a device group using the device- group browser. | Independent |
QCCR1D159987 | Unable to select for software install from Browse, but it can be done from Type. | Independent |
Software Repository |
||
QCCR1D159279 | Receive PackageRepositoryCommunicationException when trying to import an MSI:
HPSA-1468 wordbot.UNKNOWN |
Independent |
QCCR1D165735 | The agentcaches have a default refresh period of 4 hours (LONG_TTL=60*60*4). However, if there are missing agents, then this refresh is done in 5 minutes(SHORT_TTL=60*5).
All satellites and cores in the facility do the same refresh. If there are a high number of satellites talking to this core, then all the incoming queries to get the full lists of existing agents can overwhelm the Software Repository. |
Independent |
Storage Web Services Data Access Engine |
||
QCCR1D164601 | Not scalable debug code in VCValueCacheUpdater.java blocks the Web Services Data Access Engine's cache invalidator. | Independent |
Virtualization |
||
QCCR1D165974 | A hardcoded timeout of one hour is not enough to finish scanning large vCenters. | Independent |
QCCR1D156690 | vCenter 5.0 displayed as Version 4.0 when added to virtualization integrations. | VMware |
QCCR1D165860 | Fixed size on the data store when cloning a VM. | VMware |
QCCR1D162389 | RHEL6 is not displayed when you create a VM under ESX 4.0. | Linux |
Web Services Data Engine |
||
QCCR1D158653 | After HPLN import, errors about multiple non-unique patches are being seen in Web Services Data Access Engine logs. | Independent |
QCCR1D165407 | OPSWpytwist dialog causes timeout during remediations on some W2K8 servers. | Windows |
Back to the table of contents
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.
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) 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.15 and also upgrade to an SA 9.15 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.15 if you uninstall the SA 9.15 agent and reinstall an SA 9.01 (or earlier) agent (not recommended, as you will be unable to use other SA 9.15 features).
For more information about the deprecation of CDR, contact your HP Technical Support representative.
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 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.
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.
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:
The following SMOs were deprecated in 9.14:
This section discusses documentation information for 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:
This section contains corrections for existing documentation.
Property Name | Required? | Description | Example |
---|---|---|---|
agent_recert.using_cdr=<0 | 1> |
Yes | Specifies that the Agent CA push will be required when the value is set to 1. Also, the old Agent CA cleanup phase will be skipped unless the agent_recert.cleanup_old_agent_ca property is set to 1.
Valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error. Default: 1.
Note: CDR refers to Code Deployment and Rollback which has been deprecated but may still be in use. |
agent_recert.using_cdr=1 |
agent_recert.cleanup |
No | Indicates whether to clean up the old AgentCA after Core Recertification.
Cleanup of old Agent CA phase is not necessary and can be disabled. The valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error. This is an optional property. Default: 0. |
agent_recert.cleanup_old_agent_ca=0 |
In the Details: Start Order for SA Components list, item 16, opswgw-lb, should be removed. The opswgw-lb component was incorporated into the Core Gateway (opswgw-cgw) component.
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.
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".
Under the heading "Network Requirements", the first bullet:
should be changed to:
Add to Table 15 an entry for Port 8081: agentcache component
Under the heading "Required and Suggested Parameters for init.ora, Oracle 11.2.0", the following entry:
db_file_multiblock_read_count := required to be = 16
should read:
db_file_multiblock_read_count := required to be >= 16
Note: The required change is ">=" before the number "16"
As of SA 9.14, under the heading "Check for Sufficient Free Disk Space in the Tablespaces", the following SQL replaces the SQL in this section for checking free tablespace disk space:
SELECT
nvl(df.tablespace_name,'UNKOWN') name,
df.mbytes_alloc Mbytes,
df.mbytes_alloc-nvl(fs.mbytes_free,0) used,
nvl(fs.mbytes_free,0) free,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_alloc) * 100 pct_used,
nvl(df.largest,0) largest,
nvl(df.mbytes_max,df.mbytes_alloc) Max_Size,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_max) * 100 pct_max_used
FROM
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
max(bytes)/1024/1024 largest,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Mbytes_max
FROM
dba_data_files
GROUP BY tablespace_name
) df,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_free
FROM
dba_free_space
GROUP BY tablespace_name
) fs
WHERE df.tablespace_name = fs.tablespace_name(+)
UNION
SELECT
D.tablespace_name name,
D.mbytes_alloc Mbytes,
((ss.used_blocks * F.block_size) / 1024 / 1024) used,
D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024) free,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.mbytes_alloc) * 100 pct_used,
nvl(((G.max_blocks * F.block_size) / 1024 / 1024),0) largest,
Max_Mbytes Max_Size,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.Max_Mbytes) * 100 pct_pct_used
FROM
(
SELECT
tablespace_name,
used_blocks,
free_blocks,
max_size
FROM
v$sort_segment
) ss,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Max_Mbytes
FROM
dba_temp_files
GROUP BY tablespace_name
) D,
(
SELECT
B.name,
C.block_size,
SUM (C.bytes) / 1024 / 1024 mb_total
FROM
v$tablespace B,
v$tempfile C
WHERE B.ts#= C.ts#
GROUP BY B.name, C.block_size
) F,
(
SELECT
B.name,
max(blocks) max_blocks,
sum(blocks) total_blocks
FROM
v$tablespace B,
v$tempfile C
WHERE
B.ts#= C.ts#
GROUP BY B.name
) G
WHERE
ss.tablespace_name = D.tablespace_name and
ss.tablespace_name = F.name and
ss.tablespace_name = G.name;
Add the following required open port:
Step 4: The following bullet should be removed, as the truth_data.tar.gz is no longer a valid file:
Chapter 8: Satellite Installation
Remove the following bullet:
Under the heading "Uninstall a Single Core in a Multimaster Mesh", remove step 1a. This step is no longer required.
SA 9.10 User Guide: Application Configuration
typo in table 10, row 1. "... where the value will be stored in the value wet." It should say, "... where the value will be stored in the value set.”
For the RejectResponseUrl tag the range is wrong:
r'
(HTTP_URLSCAN_STATUS_HEADER)|(
HTTP_URLSCAN_ORIGINAL_VERB)|(H
TTP_URLSCAN_ORIGINAL_URL)';optional@
It should use double quotes instead of single:
r"
(HTTP_URLSCAN_STATUS_HEADER)|(
HTTP_URLSCAN_ORIGINAL_VERB)|(H
TTP_URLSCAN_ORIGINAL_URL)”;optional@
Delete [Options] and replace with [AllowExtensions]
Replace the sentence:
"The field delimiter used here will be an end of line element which instructs the parser stop reading an entry when it encounters the end of a line."
With the following sentence:
"The field delimiter used here will be an end of line element which instructs the parser to stop reading an entry when it encounters the end of a line."
Replace this in the Description column:
"sequence-delimiter=":"
Instructs the parser to read a colon ( : ) as part of the string and the point at which to move on to the next entry."
With the following:
"field-delimiter-is-eol
Instructs the parser to read the next entry up to the end of the line. "
Replace this sentence:
"Next type the following CML replace tags to define the three kay value."
With this sentence:
"Next type the following CML replace tags to define the three-key value."
Replace this sentence:
"The filename-key value is a pathname. It must start with a slash."
With this sentence:
"The filename-key value is a pathname. It does not have to begin with a slash."
Replace this range:
1024<=,<=2048
With this range:
1024<=&<=2048
Replace this sequence:
"/examples/namespace/ip"
With this one:
"/example/namespace/ipaddress = 192.168.0.1"
Replace this sentence:
"Source: The source attribute is the database key"
With this sentence:
"Source: The source attribute is the key."
Replace this sentence:
"The only required element in a replace tag is the source"
With this one:
"The only required element in a loop tag is the source"
Replace this sentence:
"The filename-key value is a pathname. It must start with a slash."
With this sentence:
"The filename-key value is a pathname. It can be written as a relative path and does not need to begin with a slash (/).""sequence-delimiter-iswhitespace"
With this one:
"sequence-delimiter-is-whitespace"
" sequence-delimiter-issemicolon "
With this one:
"sequence-delimiter-is-semicolon "
The delimiter Attribute
whitespace-delimited
comma-delimited
semicolon-delimited
tab-delimited
quote-delimited
delimiterInstruction Tag Syntax
@!whitespace-delimited@
@!comma-delimited@
@!semicolon-delimited@
@!tab-delimited@
@!quote-delimited@
@!delimiter={string}@
whitespace-delimited is the default behaviorOption Attribute Syntax
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;whitespace-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;comma-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;semicolon-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;tab-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;quote-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;delimiter={string}[;{option}]...]]]]@whitespace-delimited is the default behavior.
Description
delimiter sets the default delimiter character. If not explicitly specified, sequence-delimiter and field-delimiter will inherit this value.
Valid for replace and sequence tags.
Complete HP-UX OS Provisioning instructions are provided in the SA HP-UX OS Provisioning Whitepaper, which can be downloaded for any relevant SA 9.x release from the HP Support Self-Solve website: http://support.openview.hp.com/selfsolve/manuals or http://support.openview.hp.com/selfsolve/documents
In chapter 4:
Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import -manual
With this statement:
Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import/bin/solpatch_import --manual
When Agent uninstall is attempted on a core machine and the --force uninstall option is not provided, the following warning is prompted:
WARNING: The server is owned by the OPSWARE account. Probably it is a core machine.
Are you sure you want to uninstall the Opsware Agent? [y/n]:
If the 'n' option is selected, the Agent uninstall is aborted. Otherwise, the uninstall proceeds.
When installing the Agent on a core machine that already has the Agent installed and the --coreinstall installer option is not provided, the installation is aborted with the following error message:
You are trying to install the agent on a core machine without passing the --coreinstall argument.
Installing the opsh RPM places the OGFS shell and the Agent Upgrade Tool in the directory /opt/opsware/opsh/bin.
# cd /opt/opsware/opsh/bin
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:"
Please note the following documentation errors:
SA 9.1x support for BSAE 2.0, 2.01, and 9.12 was misstated in previous versions of the SA 9.1x Support and Compatibility Matrix.
In the HP BSA Essentials column in the Cross-Product Compatibility section, remove all references to the following: 2.0, 2.01, 9.12.
This section contains additions to existing documentation.
Enabling IBM POWER6 Provisioning with the DHCPD Tool
Due to hardware constraints, IBM POWER6 servers cannot be provisioned using the normal OS Provisioning procedures. However, you can enable provisioning for these servers using the dhcpdtool provided with SA.
This involves using the dhcpdtool to set a parameter in the initial subnet declaration which enables Linux OS provisioning on the IBM POWER6 server's hardware. This workaround also requires that SA be in Full DHCP Management mode.
Note: Setting this parameter prevents Solaris SPARC OS provisioning. You will see a warning message to this effect when you change the parameter.
Perform the following tasks to enable Linux OS Provisioning on IBM POWER6 hardware:
1. Start dhcpdtool.
/opt/opsware/dhcpd/sbin/dhcpdtool
2. Select Full DHCP Management.3. Select the network for which the workaround is to be applied. An editing menu is displayed:
Opsware DHCP Network Configuration
Editing DHCP information for 192.168.208.160/27 (255.255.255.224)
1) gateway : 192.168.208.161
2) DHCP range : 192.168.208.163 - 192.168.208.190
3) DNS servers: 192.168.194.4
4) DNS domain : dev.opsware.com
5) Power6 provisioning override: No
!!! WARNING: Option 5) breaks Solaris SPARC OS provisioning !!!
!!! Make sure to deactivate this option before trying to provision a Solaris SPARC machine !!!1..5 to edit option.
d)elete network and return to main menu.
k)eep network and return to main menu.Choice [1..5, d, k]:
4. Select option 5 and press ENTER
5. The message “Are you sure that you want to toggle POWER6 provisioning although it breaks Solaris SPARC provisioning (Enable/Disable)?” is displayed.
6. Press E to Enable POWER6 provisioning, D to Disable, select K to keep the settings, then S to save them.
7. Exit the DHCPD tool. Upon exiting, the DHCPD server is restarted and the new setting takes effect.
Note: If you are not using the SA-provided DHCPD server, you must add the following line to the subnet in which POWER6 you will perform OS provisioning:
filename "yaboot";
Chapter 8: Satellite Installation
- word_tmp_dir: directory where Package Repository will temporarily place content during uploads
- word.store.host: the host name of the server where Software Repository content is stored.
- media_server.windows_share_name: the share name to use for the Windows media sharing server (note: share names that are longer than 8 characters may give errors while browsing or may not be accessible to some older clients.)
- media_server.windows_share_password: the password to write-protect the Windows media share. Import_media tool will prompt for this password each time it is run.
Satellite Free Disk Space Requirements
This section describes the free disk space (in addition to the operating files system) requirements for any SA Satellite.
Satellite Component Directory | Recommended Free Disk Space |
---|---|
/opt/opsware | 15 GB |
/var/log/opsware | 10 GB |
/var/opt/opsware | 20 GB
(dependent on caching plans and the core cache size) |
/osmedia | 15 GB
(dependent on OS Provisioning needs) |
The first bullet should read:
" The tnsnames.ora file must reside in the following locations:
Add the following custom attribute to Table 9:
Timeout
Values: the number of minutes to wait for Linux provisioning to complete before timing out.
Default: 30 minutes
If Linux provisioning fails because the job takes too long to complete, you can specify a longer timeout period.
Back to the Table of Contents
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.
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.
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 2000-2013 Hewlett-Packard Development Company, L.P.
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.
New Publication Date | Change |
07-31-2013 | Removed QCCR1D167727 |
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. |
1/5/2015 | Added the following section (should have been carried over from previous release notes): Operating System Build-Plan Script Changes. |
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