HP Matrix Operating Environment Software User Manual
Page 211
Service creation fails using RDM disk with high availability Hyper-V template
When creating a service request using RDM disks with high availability, properties must be enabled
in the Matrix OE logical server management and Matrix infrastructure orchestration properties files,
or service creation fails and the following message appears:
The specified configuration is not supported. A physical disk cannot be
connected to a High Availability Hyper-V template. Modify the template
Issue
and deselect High Availability, or connect virtual storage to the
template instead of physical storage.
Properties were not enabled in the Matrix OE logical server management and Matrix infrastructure
orchestration properties files.
Possible cause
Action
• For Matrix OE logical server management:
Go to C:\Program Files\HP\Virtual Server Environment\conf\lsa.
1.
2. Edit the lsa.properties file by setting the HA_VM_RDM_ENABLED property to true:
3. Restart the Matrix OE logical server management service.
• For Matrix infrastructure orchestration:
1. Go to C:\Program Files\HP\Matrix infrastructure orchestration\conf.
2. Edit the hpio.properties file by setting the hyperv.ha.vm.rdm.enabled property
to true.
3. Restart the Matrix infrastructure orchestration service.
Create Service request with 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:
Issue
• 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
Suggested action 1. Perform manual cleanup, see the Manual clean-up process (physical) in the HP Matrix Operating
Environment Infrastructure Orchestration User Guide at Refer to Manual cleanup for HP Insight Control server provisioning.
2. Recreate the service request in Matrix infrastructure orchestration.
After crash, VMS are available on VCenter and request fails
If the IO service is stopped during provisioning operation, under some circumstances after the
service is restarted, IO may not be able to delete all of the VM instances that were in progress.
Issue
VMs that were in progress at the time of the service restart may not be uniquely identified as created
by IO, and consequently cannot be safely deleted.
Possible cause
The request history will indicate that it was unable to successfully cleanup the failed request. Check
to see if the indicated VMs are still present on the hypervisor, and manually perform cleanup/deletion
of the VMs as needed.
Suggested action
Service creation
211