Unable or failed to delete Page 181
Page 181
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
Please clean up the directory manually.
•
Failed to delete VM
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.
For Hyper-V:
1.
Connect to the Hyper-V hypervisor.
2.
Delete the VM from the Hyper-V Manager (if it has not already been deleted).
3.
Navigate to the directory and delete the offending directory and directory contents.
If HP Server Automation (SA) deployment was used to provision the VMs:
1.
Remove the ESX and/or Hyper-V VMs using the preceding steps.
2.
Connect to the SA server.
3.
From the HP Server Automation (SA) “Devices” view, select the VMs.
4.
Perform a “deactivate” and a “delete.”
New servers do not appear in the Unassigned pool
New servers do not appear in the infrastructure orchestration Unassigned pool.
Issue
Resources are added to the Unassigned pool when infrastructure orchestration recognizes that they
are available and are licensed and configured correctly. By default, infrastructure orchestration
Possible cause
discovers and updates the available resources once an hour. Recently added resources are available
only in the infrastructure orchestration Unassigned pool after 1 to 2 hours (depending on the
discovery process of the other products, such as Insight Control virtual machine management, VCEM,
and Matrix OE).
Action
•
From the Matrix OE management screen, select Tools
→Logical Servers→Refresh to refresh Matrix
OE and activate the changes. From infrastructure orchestration screen, click on Servers tab and
then click Refresh to trigger a refresh of servers inventory.
•
Perform a Systems Insight Manager Discovery. A server must be discovered at the Systems Insight
Manager level through the IP address discovery mechanism before it can be used in infrastructure
orchestration. VM Hosts must be registered with Insight Control virtual machine management.
•
Ensure that servers are licensed for Matrix OE.
•
Ensure that VMware ESX hosts have a full ESX license (not a base license).
Service creation
181