HP Matrix Operating Environment Software - Manual (Page 92)

•
Valid users are no longer associated with templates.
•
Provisioning a virtual machine failed with a VM must be powered off for customization error
message.
•
Provisioned VMs fail due to improper VM host hardware configuration.
•
VM host server blade is not returned to server pool as Unused when VM host service is deleted.
•
Task for logical server has failed. Failure: Service console load average on the
source server is greater than the threshold value.
•
Storage Pool Entries defined in Insight Dynamics might not appear under the Storage page
in Insight Orchestration.
Error deploying logical server from _ls realized by
vm:///vmfs/volumes/....vmx/. Copy virtual
Failure message
machine failed: Unable to access file
[inactive-datastore-name]vmware-template-name/vmware-template-name.vmdk.
In the message above, “/.../” represents the datastore allocated for the VM;
[inactive-datastore-name
]” represents the datastore on which the template resides.
The template selected for provisioning an ESX VM resides on an inactive datastore. Possible cause
Do one of the following: Action
•
Activate the datastore on which the selected VMware template resides.
•
In Insight Orchestration Designer, select a different VMware template for provisioning the ESX
VM.
The start function on virtual machine failed: There
are not enough licenses installed to perform the operation.
Failure message
ESX host not licensed. Possible cause
Use vCenter to apply a full ESX license to the host. Action
Select or create an empty folder as the target destination. Failure message
The directory that Insight Orchestration is attempting to deploy to is not empty, probably due to a
previous failed provisioning which was not cleaned up completely. Possible cause
When Insight Orchestration deploys a virtual machine, it creates a directory structure into which
the virtual machine is provisioned. The directory that is created follows the pattern: Action
Volume>\\ . This folder contains all the folders and files
corresponding to the virtual logical servers. Delete this folder and all its contents.
For ESX, the easiest way to accomplish this is to use the vCenter client to browse the ESX servers
datastore, then navigate to the directory and delete the offending directory and directory contents.
Failure message •
Unable to delete on , VM may still exist.
Please clean up the directory manually.
•
Failed to delete VM from . Please clean up
the directory manually
A provisioning failure occurred and Insight Orchestration lost communication with the virtual machine
hosts. As a consequence, Insight Orchestration was unable to complete the deletion of the virtual
machines. Possible cause
When Insight Orchestration deploys a virtual machine, it creates a directory structure into which
the virtual machine is provisioned. The directory that is created follows the pattern: Action
Volume>\\ . This folder contains all the folders and files
corresponding to the virtual logical servers. Delete this folder and all its contents.
92 Troubleshooting