-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ruby Vers. Issue? #36
Comments
Please add --debug option in your "vagrant up" commands, more details then. |
Okay that worked out better, but I still can't figure out what the problem is. Here's the debug output, thanks Henry: INFO global: Vagrant version: 1.4.2 |
it seems that your connection to vSphere platform timeout. Could you please provide the command and configuration you triggered? I guess the values may be not correct in vSphere parameters. |
The command I issued was: "vagrant up --provider=vsphere" Here's what's in my vagrantfile: VAGRANTFILE_API_VERSION = "2" Vagrant.configure("2") do |config| config.vm.box = 'dummy' config.vm.provider :vsphere do |vsphere| end Is this what you're looking for? I have the vCenter up and running with an ubuntu template that i cloned from an existing ubuntu VM I created. I've attached two screenshots of my vCenter. |
Ensure your values matched to the meaning of each param, attached with a screenshot of my vsphere platform. Vagrant.configure("2") do |config|
config.vm.box = 'dummy'
config.vm.box_url = 'dummy.box'
config.vm.provider :vsphere do |vsphere|
# vCenter Address
vsphere.host = '10.202.241.x'
# Data Center Name
vsphere.data_center_name = 'ICS'
# ESX Host Address
vsphere.compute_resource_name = '10.202.241.1'
# Resource Pool Name
vsphere.resource_pool_name = 'sample'
# Template PATH
vsphere.template_name = 'VagrantTemplate/vsphere-vagrant-box-v0.3'
#vsphere.customization_spec_name = 'vm-example'
# Data Store Name
vsphere.data_store_name = 'datastore'
# New VM Name
vsphere.name = 'Zenoss'
# vCenter Username and Password, not machine username/password
vsphere.user = 'xxxx'
vsphere.password = 'xxxx'
# Avoid SSL Certificate Issue
vsphere.insecure = true
end
end |
I'll double check my settings once I get home. As for the dummy.box, i just tar after downloading the .json file from here. That's correct right? I'm assuming if I download one of the vmware boxes "precise64" from their website and turn it into a template, that should work... Thanks again, Henry. I'll keep you posted on the results. |
Quick question. Is the dummy.box supposed to be a base box? I also am a little confused on the template_name parameter. I thought it was supposed to point to an existing template on the vsphere server. But those templates can only be created from existings VMs. How do you go from a .box file to a template file? I downloaded an ubuntu vmware base box (precise64_vmware) from the www.vagrantbox.es website. |
dummy.box
template_name
|
Thanks again Henry, jumping back on this and will update once I figure it out |
Just as a quick note I had connection issues for a while and then I added the vsphere.insecure = true as my cert was failing validation since I was running in a private network that had no cert. This may be something you want to try. |
Any news on this yet. I seem to be experiencing similar trouble. (high-level config; vCenter server appliance v5.5, ESXi 5.1 and 5.5 mixed, AD integration enabled) |
I actually had to put this on hold as a few other things came up. Will be jumping back on this project soon though and I'll update it with any progress. |
Ok, no prob. I just started out testing with Vagrant on our vSphere dev On Wed, Feb 12, 2014 at 12:55 AM, rascboy notifications@github.com wrote:
|
Try using rbvmomi directly to connect to vsphere. You will get much better error output. |
Hy I also get this error using a vagrant box that worked just fine until 14th of December I belive, when it suddenly started giving this error:
my Cheffile only contains vim cookbook from site "https://supermarket.chef.io/api/v1" If I am offtopic please ignore this. |
@mihai-mocanu that error is due to having bad or out of date certificates on your local box. You need to either put the certificates in place or set |
Thanks, but I already tried that, with no luck. I still get the same error. |
I'm not exactly sure what's going on but I'm getting this output when trying to Vagrant up w/ the vsphere plugin:
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'/root/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/trivial_soap.rb:56:in
restart_http' /root/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/trivial_soap.rb:20:in
initialize'/root/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/connection.rb:31:in
initialize' /root/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/vim.rb:36:in
new'/root/.vagrant.d/gems/gems/rbvmomi-1.8.1/lib/rbvmomi/vim.rb:36:in
connect' /root/.vagrant.d/gems/gems/vagrant-vsphere-0.7.0/lib/vSphere/action/connect_vsphere.rb:15:in
call'/opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/warden.rb:34:in
call' /opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/builtin/config_validate.rb:25:in
call'/opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/warden.rb:34:in
call' /opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/builder.rb:116:in
call'/opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/runner.rb:69:in
block in run' /opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/util/busy.rb:19:in
busy'/opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/action/runner.rb:69:in
run' /opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/machine.rb:147:in
action'/opt/vagrant/embedded/gems/gems/vagrant-1.4.2/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
Any ideas on what's going on with this? I did a fresh VM install so the machine pretty much just has requirements for vagrant-vsphere installed... Thanks!
The text was updated successfully, but these errors were encountered: