stack trace on "vagrant up --provider=vsphere"

[tehranian]

Hi there,

How can I figure out what the issue is here:

$ vagrant up --provider=vsphere
Bringing machine 'default' up with 'vsphere' provider...
/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect'
/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `block in connect'
/Applications/Vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect'
/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:857:in `start'
/Users/tehranian/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/trivial_soap.rb:56:in `restart_http'
/Users/tehranian/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/trivial_soap.rb:20:in `initialize'
/Users/tehranian/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/connection.rb:31:in `initialize'
/Users/tehranian/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/vim.rb:36:in `new'
/Users/tehranian/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/vim.rb:36:in `connect'
/Users/tehranian/.vagrant.d/gems/gems/vagrant-vsphere-0.7.0/lib/vSphere/action/connect_vsphere.rb:15:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builder.rb:116:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/machine.rb:147:in `action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
No error message

It doesn't seem to be making any outbound http connection to vSphere, as the whole invocation fails within 1/2 second.

FWIW I'm running OS X Mavericks and am seeing this with Vagrant 1.4.3 and 1.5.1.

Thanks,
Dan

[tehranian]

Hmmm, I get the same stack trace when I try this on an Ubuntu 12.04 LTS machine as my original OS X Mavericks machine.

[juliacollins]

Hi Dan,

Could you confirm that you're building the gem from the latest version (0.7.1)? It restricts the version of rbvmomi to 1.6.x and may solve your problem.

Julia

[tehranian]

Hi Julia,

When I follow the plugin's installation instructions I get version 0.7.0 of the gem. Looking at the gem repo, I do not see a version 0.7.1 having been published yet. Ex:

$ vagrant plugin update vagrant-vsphere
Installing the 'vagrant-vsphere' plugin. This can take a few minutes...
Installed the plugin 'vagrant-vsphere (0.7.0)'!

$ gem list vagrant-vsphere --remote --all
*** REMOTE GEMS ***
vagrant-vsphere (0.7.0, 0.6.0, 0.5.1, 0.5.0)

Are you saying I should clone the git repo and install the non-released 0.7.1?

Thanks,
Dan

[tehranian]

FWIW the README.md says that 0.7.1 is available on RubyGems.org but when I go there I see 0.7.0: https://rubygems.org/gems/vagrant-vsphere

[flamingbear]

Hi Dan,
I apologize for that, It's taking a little longer to get the rubygem pushed. I reached out to the original developer and had the wrong email address so getting a gem on RubyGems.org is taking just a bit longer than expected. I'm in touch with Andy and expect this to be remedied very shortly.

Thanks for your patience.
Matt

[flamingbear]

Hi Dan,

And like that we're back. I think you should be able to pull the latest 0.7.1 version from rubygems.org now.

Cheers,
Matt

[tehranian]

Thanks all. I was able to install "vagrant-vsphere-0.7.1" which depends on "rbvmomi-1.6.0". Unfortunately I'm still getting the same stack trace upon "vagrant up" on both OS X Mavericks and Ubuntu 12.04.

vagrant@my-vm:~$ v up --provider=vsphere 
Bringing machine 'default' up with 'vsphere' provider...
/opt/vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect'
/opt/vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `block in connect'
/opt/vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/opt/vagrant/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect'
/opt/vagrant/embedded/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
/opt/vagrant/embedded/lib/ruby/2.0.0/net/http.rb:857:in `start'
/home/vagrant/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/trivial_soap.rb:56:in `restart_http'
/home/vagrant/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/trivial_soap.rb:20:in `initialize'
/home/vagrant/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/connection.rb:31:in `initialize'
/home/vagrant/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/vim.rb:34:in `new'
/home/vagrant/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/vim.rb:34:in `connect'
/home/vagrant/.vagrant.d/gems/gems/vagrant-vsphere-0.7.1/lib/vSphere/action/connect_vsphere.rb:15:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/runner.rb:69:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/action/runner.rb:69:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/machine.rb:157:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/batch_action.rb:72:in `block (2 levels) in run'
No error message

[PierrePaul]

I've got the same issue as well. By adding a bit of debugging I got : VagrantPlugins::VSphere::Action::Clone::Error

Will try to find what's going on.

[PierrePaul]

For testing purposes I've put a vsphere.template_name = 'lorem ipsum' in my Vagrant file. Of course the template/vm 'lorem ipsum' doesn't exist and vagrant-vsphere was crashing. Maybe we should check if the template exists before doing... what exactly?

[sneal]

running VAGRANT_LOG=debug vagrant up --provider=vsphere I see another error before this:

 INFO warden: Calling IN action: #<VagrantPlugins::VSphere::Action::Clone:0x00000002f0b728>
ERROR warden: Error occurred: NoPermission: Permission to perform this operation was denied.
...
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/connection.rb:61:in `parse_response'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/connection.rb:90:in `call'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/basic_types.rb:203:in `_call'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/basic_types.rb:74:in `block (2 levels) in init'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/vim/Folder.rb:7:in `find'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/vim/Folder.rb:83:in `traverse'
/home/teamcity/.vagrant.d/gems/gems/rbvmomi-1.6.0/lib/rbvmomi/vim/ServiceInstance.rb:8:in `find_datacenter'
/home/teamcity/.vagrant.d/gems/gems/vagrant-vsphere-0.7.1/lib/vSphere/util/vim_helpers.rb:8:in `get_datacenter'
/home/teamcity/.vagrant.d/gems/gems/vagrant-vsphere-0.7.1/lib/vSphere/action/clone.rb:22:in `call'

The clone step is attempting to find my data center - which is failing. Using the same data center and user with knife vsphere works fine. Not sure what's going on.

[johnsmyth]

Did anyone find a resolution to this? I'm experiencing the exact same issue....

[PierrePaul]

@johnsmyth Are you sure your template has no typo and is accessible?