Service creation fails with internal error – HP Matrix Operating Environment Software User Manual

Page 174

Advertising
background image

Service creation fails with a virtual machine customization error

Create Request fails with a virtual machine customization error.

Issue

Possible cause

The environment is not completely configured

The virtual machine used in the virtual machine management template was not powered off
cleanly

If the environment is not completely configured, requests might fail when executing the virtual
machine customization step. Issues can include missing the sysprep folder on the vCenter Server,
insufficient licenses on the vCenter Server, or attempting to customize a virtual machine with a guest
operating system that is not supported on the vCenter Server.

Action

Verify that the environment is correctly configured and provisioning a supported guest operating
system. For more information on configuration, see HP Insight Management Installation and
Configuration Guide
available at

http://www.hp.com/go/insightcontrol/

.

Power off the virtual machine cleanly before creating the virtual machine management template.

Hyper-V host changes UUIDs of VMs with simultaneous create service requests

When 10 or more Create Service requests reach a Hyper-V VM host at the same time, the Hyper-V
host changes the UUID of some of the VMs.

Issue

Input provided by IO: Note the UUID shown in value=.

Failure message

2012-05-22 07:04:29,682 | DEBUG | RMI TCP Connection(18256)-172.16.101.0

| 8026 | Entering |

setDeviceProperty(config=vmfile://172.16.0.161/E:\VSE_VirtualMachines\

Template1_5_22_c_testCirotest06, device=BIOSSerial, prop=BIOSGUID,

value=2EFDF6C5-8FAE-9C41-BB68-DF1598E3BCB4) | 1337681069682

VM Details in Insight Control virtual machine management: Note the UUID in biosID= is different
than shown above.

vm://172.16.0.161/E:\VSE_VirtualMachines\Template1_5_22_c_testCirotest09\Virtual

Machines\2BC14013-0967-46EC-AFDC-E0A743A5626B.xml biosId =

C11CA80F-C9A0-4891-B213-5CC78A09FCFC

Action

Specify a larger boot disk size to create a sufficient time difference between the parallel requests,
or

Create the VMs on two or more different Hyper-V VM hosts.

Service creation fails with internal error

A Create Service request fails on ESX or Hyper-V with an error similar to the following: “Failed,
Task for Logical Server ESXre301 has failed. Logical server job completed with a failure status.
Failure: Internal Error (Error occurred while executing deploy template Operation: null)."

Issue

This error is displayed during startup of the Systems Insight Manager and Insight Control virtual
machine management services. The issue can occur during an upgrade, during a restart of services

Possible cause

after data migration, or during a restart of the CMS. The timing of these services becoming fully up
and running can lead to a small window of time that results in incorrect initialization of data.

Restart the Insight Control virtual machine management service and retry the create service request.

Action

Service creation fails with “Unable to locate boot disk path”

A Create Service request fails on ESX or Hyper-V with an error similar to the following: “Unable to
locate boot disk path H:\VSE_VirtualMachines for logical server {logical_server}_ls. VM host

Issue

174

Troubleshooting

Advertising