Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

Timeout during template clone #118

Open
otwieracz opened this issue Aug 4, 2017 · 4 comments
Open

Timeout during template clone #118

otwieracz opened this issue Aug 4, 2017 · 4 comments

Comments

@otwieracz
Copy link

While trying to clone template to VM using vagrant-vsphere I am running into timeout error after 5 minutes:

==> default: Calling vSphere CloneVM with the following settings:
==> default:  -- Template VM: pcc-149-56-104-121_datacenter2487/vm/Templates/Linux/centos-7-server
==> default:  -- Target VM: pcc-149-56-104-121_datacenter2487/vm/TEST/kitchen-cookbooks-default-centos-7-server_default_1501830422774_3121
STDERR: Undefined namespace prefix: //soapenv:Body/*
---- End output of vagrant up --no-provision --provider vsphere ----
Ran vagrant up --no-provision --provider vsphere returned 1] on default-centos-7-server

The issue is also described here:
nsidc/vagrant-vsphere#106

Seems like in my case, on OVH Private Cloude (vSphere 6), timeout is more or less after 5min:

I, [2017-08-04T09:21:09.865227 #30699]  INFO -- Kitchen: -----> Creating <default-centos-7-server>...
E, [2017-08-04T09:26:23.183730 #30699] ERROR -- Kitchen: ------Exception-------
E, [2017-08-04T09:26:23.183807 #30699] ERROR -- Kitchen: Class: Kitchen::ActionFailed
@jrgarcia jrgarcia self-assigned this Aug 4, 2017
@otwieracz
Copy link
Author

vagrant-vsphere uses .wait_for_completionwhich timeouts on the vSphere side.

@otwieracz
Copy link
Author

What I can suggest is to, instead of .wait_for_completion, ask every a while if the VM is already cloned.

@jrgarcia
Copy link
Contributor

I'm not sure there is much I can do about this from the rbvmomi side. What you mentioned should work. You can increase the timeout for rbvmomi, but if the provider is where the timeout is occurring, I'm not sure what I could offer.

@otwieracz
Copy link
Author

How can I check if object returned fromtemplate.CloneVM_Task(folder: vm_base_folder, name: name, spec: spec) is complete other than .wait_for_completion? Do you have any idea about possible re-implementation of wait_for_completion in form of polling loop?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants