HP Matrix Operating Environment Software User Manual
Page 87

•
Error deploying logical server from <vm-hostname>_ls realized by
vm://<vmhost-ip>/vmfs/volumes/...<vm-hostnames>.vmx/. Copy virtual
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.
Failure message
The template selected for provisioning an ESX VM resides on an inactive datastore.
Possible cause
Do one of the following:
•
Activate the datastore on which the selected VMware template resides.
•
In Insight Orchestration Designer, select a different VMware template for provisioning the
ESX VM.
Action
The start function on virtual machine <logical_server_id> failed: There
are not enough licenses installed to perform the operation.
Failure message
ESX host not licensed.
Possible cause
Use Virtual Center 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: <VMFS
Volume>\<Service Name>\<VM Name>
. 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 Virtual Center client to browse the ESX
servers datastore, then navigate to the directory and delete the offending directory and directory
contents.
Action
•
Unable to delete <vm name> on <host:path/to/vm>, VM may still exist.
Please cleanup the directory manually.
•
Failed to delete VM <vm name> from <host:path/to/vm>. Please cleanup
the directory manually
Failure message
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: <VMFS
Volume>\<Service Name>\<VM Name>
. 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 Virtual Center client to browse the ESX
servers datastore, then navigate to the directory and delete the offending directory and directory
contents.
Action
Working with services
87