HP Matrix Operating Environment Software - Manual (Page 159)

Error deploying logical server: Copy virtual machine failed: Unable to access file
vmware-template-name.vmdk
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 infrastructure orchestration designer, select a different VMware template for provisioning the
ESX VM.
Start function on virtual machine failed: there are not enough licenses installed to perform the
operation
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
Select or create an empty folder as the target destination. Failure message
The directory that infrastructure 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 infrastructure 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.
Unable or failed to delete
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 infrastructure orchestration lost communication with the virtual
machine hosts. As a consequence, infrastructure orchestration was unable to complete the deletion
of the virtual machines. Possible cause
When infrastructure 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:
1. Use the vCenter client to browse the ESX server's datastore.
2. Navigate to the directory and delete the offending directory and directory contents.
Service creation 159