VMware Cloud Community
markajohnson
Contributor
Contributor

Clone of VM Fails

I'm trying to clone a RHEL 6.0 VM in VCloud Director and get this error:

A general system error occurred: The virtual machine requires the vcloud1/system.service.vmware.vsla.vcloud1 service, which is not available on the host.

The VM was created from a template and was created successfully.

Here's the clone request:

POST: https://192.168.30.61/api/v1.0/vdc/1496754145/action/cloneVApp

<?xml version="1.0" encoding="UTF-8"?>
<CloneVAppParams name="temp-clone-6558"
xmlns="http://www.vmware.com/vcloud/v1"
xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" >
<Description>Clone of av-74.114-DER1-vCloud-SM Linux (RHEL 6.0 x64) Server-SM QA vCloud Director v1.0-1</Description>
<Source href="https://192.168.30.61/api/v1.0/vApp/vapp-702999489"/>
<IsSourceDelete>false</IsSourceDelete>
</CloneVAppParams>

Other VMs clone just fine.  Any ideas?

Thanks,

Mark

Reply
0 Kudos
5 Replies
admin
Immortal
Immortal

To me it sounds like it's not finding the vCD agent on the ESX host where the vApp is being instantiated. Are you sure your hosts are correctly prepared and that this particular vApp isn't being cloned to a host that wasn't touched by your other (successful) clones?

Reply
0 Kudos
markajohnson
Contributor
Contributor

As a matter of fact, one of the esx hosts is not prepared.  The status shows DISABLED, NOT READY, but AVAILABLE.  There appears to be some problem with going into maintenance mode so the prepare is failing.  Could this be the cause?

When I manually try to copy the VM using the VCloud Director UI, the copy succeeds.  When I use the CloneVApp call as above, the copy fails.  Is there some way to specify which host to use?  I don't see that as a parameter in the CloneVAppParams structure.

Reply
0 Kudos
admin
Immortal
Immortal

Yes, that is likely the cause. In order to install the vCD agent on newer versions of ESXi it needs to enter maintenance mode. Once the agent is installed it will exit maintenance mode. You could try to manually install the VIB: http://kb.vmware.com/kb/2003486

It's not possible to specify the target host – it's not "cloudy" enough. Smiley Wink You could try to influence it by disabling other hosts, but your best bet is to just prepare it and be done with it.

Reply
0 Kudos
markajohnson
Contributor
Contributor

I am not able to install this software at this time due to other constraints on the environment.  We will do this durning the next maintenance window.  However my "bad" host appears disabled - why would it be used?  And I don't see any options in the UI to disable the host.  The other hosts have an option to Disable them, but that option is grayed out on this particular host

Again, other VApp's can be copied.  Is it possible the VApp has some sort of reference to a partucular esx host?

Second, if I use the vCD UI to "Copy" the VApp, it works without errors.  Is the UI using some other API call to perform the copy/clone?

Thanks for the help.

Mark

Reply
0 Kudos
jhunter11
Contributor
Contributor

I'm having a similiar issue.  We recently added another host to the cluster, but even though in the VCD UI the host is listed as unavailable and unready, when I was trying to clone or move VMs from one vApp to another, it was trying to put them on this new host and failing.  Our solution was to put the host in maintenance mode.  That will work until it's prepped and ready to be used, but still I don't think that should be happening in the first place.

Reply
0 Kudos