HP Matrix Operating Environment 7.3 Update 1 Release Notes

Task for Logical Server has failed. Logical server job
(logicalservername_FQDN) completed with a failure status.
Failure: At least one OS or software deployment has failed
In the Insight Control server provisioning appliance console, the following error appears:
Wait for HPSA Agent failed with exit code 6 at step 21
Suggested Action
1. Perform manual cleanup, see the Manual clean-up process (physical) in the HP
Matrix Operating Environment Infrastructure Orchestration User Guide at Enterprise
Information Library. Refer to Manual cleanup for Insight Control server provisioning.
2. Recreate the service request in Matrix infrastructure orchestration.
Create Service request with Insight Control server provisioning fails when
deploying RHEL 5.9 OS
The installation of RHEL 5.9 OS fails with the following messages:
In Matrix OE, the following error appears on the infrastructure orchestration Requests
screen and the failed server is moved to the maintenance pool:
Task for Logical Server has failed. Logical server job (ID =
logicalservername_FQDN completed with a failure status. Failure:
At least one OS or software deployment has failed.
In the Insight Control server provisioning appliance console, the following error appears:
Monitor Installation with exit code 1 at step 19
The target server remains in LinuxPE in maintenance server mode.
Suggested Action
1. Perform manual cleanup, see the Manual clean-up process (physical) in the HP
Matrix Operating Environment Infrastructure Orchestration User Guide at Enterprise
Information Library. Refer to Manual cleanup for Insight Control server provisioning.
2. Recreate the service request in Matrix infrastructure orchestration.
Delete service request leaves "clean-me" logical servers when used with Integrity
servers if disk is not erased before delete service request
After successfully provisioning a physical Integrity server blade (using Ignite-UX, or
through a secondary CMS in a federated CMS environment), there are manual steps
you must perform to allow the disk to be erased during de-provisioning. Erasing the
disk is part of a successful de-provisioning (delete request) for an Integrity service.
If the disk is not erased, the delete service request may fail and “clean me” logical
servers will remain. In that case, a manual cleanup procedure is required. (See the
Suggested action for the cleanup procedure.)
Before you start a delete service request from infrastructure orchestration:
1. Make sure that the Integrity service was successfully provisioned (the Integrity
service is running).
2. Discover the Integrity blade where the Integrity service is running using its IP address
from Systems Insight Manager. In a federated CMS environment, discover the
Integrity blade on the primary CMS using its IP address from Systems Insight
Manager. The Integrity node's identification information should contain the UUID
and UUID (logical). You can discover the blade in either of the following ways:
30