HP Matrix Operating Environment 7.3 Release Notes

Doing so will cause the Matrix OE post-install customization step to fail with an error stating Error
customizing Logical Server Logical server name realized by target UUID.
Suggested action
Matrix OE environments can have the newly provisioned server join the domain via an OO
workflow.
NOTE: When utilizing the PowerShell PSExec command, the OO RSJRAS service should be run
as administrator.
Minor issues
IO and LSM lose DAS disk configurations after an upgrade to Insight Management 7.3
If you have logical servers configured with local disks or DAS, the upgrade process is unable to
retain any disk-related definitions. Logical server management does not support DAS disks like
SAN-based disks. DAS disks are associated only with specific blades. So, in this case, the
administrator must manually perform the DAS disk configuration post upgrading to Insight
Management 7.3.
Suggested action
In order to retrieve and save the correct configuration, the administrator must export all the definitions
for the disks in use in a XML format . This can be done by entering the following command before
the upgrade:
lsmutil -export -an -file c:\[file name].xml.
After the 7.3 upgrade, restore all the definitions by entering the following command:
lsmutil -import -an -file c:\[file name].xml.
Provisioning of Integrity VMs with NPIV disks with storage pool entries containing both
boot and data volumes may fail
Provisioning of Integrity VMs with NPIV disks may fail if the storage pool entry selected has both
boot and data entries. The following error appears
Failed while deploying operating system for service <service-name>.
Cause: Logical server job (ID = <Logical-server-job-id>) completed with
a failure status. Failure: An unexpected error has occurred. Check
Alc1_0.0.log and HP SIM log files under HP SIM logs directory for
additional details
Suggested action
When creating a service from a template containing physical boot and data disks, create a separate
storage pool entry for each boot disk.
Create Service request with Insight Control server provisioning fails as installation hangs
at 60% when deploying SLES11 SP3 OS
The installation of SLES11 SP3 hangs on the target server 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:
Failed while deploying operating system for service. Cause: Logical
Server job has failed. Logical server job completed with a failure
status. Failure: At least one OS or software deployment has failed.
Check the Deployment Service to diagnose the details.
In the Insight Control server provisioning appliance console, the following error appears:
Failed to integrate HP SA Agent at Step 19
26 Issues and suggested actions