This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
Vagrant 1.6.x - Shell provisioner problem #47
Comments
|
I've tried your Vagrantfile settings for the provisioner, and indeed it fails ... Then I tried a Puppet Provisioner, and it worked. Replaced node_config.vm.provision 'shell', path: 'scripts/provision.sh'By node_config.vm.provision :puppet do |puppet|
puppet.manifests_path = 'puppet/manifests'
puppet.manifest_file = 'site.pp'
puppet.module_path = 'puppet/modules'
# puppet.options = "--verbose --debug"
endI wonder if this isn't a Vagrant 1.6.0 issue (reproduced it on 1.6.1 too), or like a new internal process we are not really aware when developing a vagrant plugin. |
|
Can you try the following patch @StefanScherer ?
If you could validate it against your vagrant 1.5.x environment too ? |
|
I have commented out that line and built the vApp again. The first VM web-vm is ok, but there is a problem to ssh into the second VM ssh-vm. This is the rest of the debug output: |
|
Hmm, can you give it another try, as I see it's a network problem from this line: I did try it with your Vagrantfile settings on my setup and 3 VMs and it seems fine. |
|
Yes, I have seen this error, too. I think, my VPN connection dropped (once again). I will clean my edge gateway settings and try again. |
|
OK, next run. Now both VM's are created and powered on and provisioned. |
StefanScherer
added a commit
to StefanScherer/vagrant-vcloud
that referenced
this issue
May 12, 2014
* upstream/develop: (32 commits) Fixes frapposelli#54 - Added vShield Edge Gateway name Fixes frapposelli#54 - Added vagrant vcloud --redeploy-edge-gw Fixes frapposelli#45 - vCloud Auth token issue Fixes frapposelli#53 - Restructure vagrant vcloud-status to vagrant vcloud <namespace> Fixes frapposelli#52 - Missed autoload Fixes frapposelli#52 - Block Ability to ssh into halted/suspended VMs Fixes frapposelli#47 - Shell provisioner error Finally fixed API Version checker to work as expected version bump. Keep waiting on task if it is in 'queued' or 'preRunning' status Update README.md Version bump Modularized the destroy part to fix issue frapposelli#43 - Split poweroff.rb into poweroff_vapp.rb and poweroff_vm.rb. - Split destroy.rb into destroy_vapp.rb and destroy_vm.rb. - Added is_last_vm.rb to check if vApp has a single VM remaining. also show vapp to vm rules fix cygdrive path for rsync cache return value of get_vapp_edge_public_ip added optional vapp_prefix to name the vapp removed set_edge_gateway_rules, no longer needed add_edge_gateway_rules for DNAT rule per port removed edge_gateway_rules code from power_on ...
StefanScherer
pushed a commit
to StefanScherer/vagrant-vcloud
that referenced
this issue
May 13, 2014
* upstream/develop: Fixes frapposelli#54 - Added vShield Edge Gateway name Fixes frapposelli#54 - Added vagrant vcloud --redeploy-edge-gw Fixes frapposelli#45 - vCloud Auth token issue Fixes frapposelli#53 - Restructure vagrant vcloud-status to vagrant vcloud <namespace> Fixes frapposelli#52 - Missed autoload Fixes frapposelli#52 - Block Ability to ssh into halted/suspended VMs Fixes frapposelli#47 - Shell provisioner error
StefanScherer
pushed a commit
to StefanScherer/vagrant-vcloud
that referenced
this issue
May 13, 2014
* upstream/develop: Fixes frapposelli#54 - Added vShield Edge Gateway name Fixes frapposelli#54 - Added vagrant vcloud --redeploy-edge-gw Fixes frapposelli#45 - vCloud Auth token issue Fixes frapposelli#53 - Restructure vagrant vcloud-status to vagrant vcloud <namespace> Fixes frapposelli#52 - Missed autoload Fixes frapposelli#52 - Block Ability to ssh into halted/suspended VMs Fixes frapposelli#47 - Shell provisioner error
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@StefanScherer has identified a problem with Vagrant 1.6.x and the Shell Provisioner
Below an extract of #45:
Stefan Scherer wrote:
But there still are some disconnects while setting up the first VM, here directly after powering on the machine:
and another disconnect after the POST for the edge gateway port forwarding rules:
But your code change stabilizes the plugin. Thanks!
And the disconnect/reconnects could be optimized later.
But I encounter another problem after rsyncing the folder into the guest:
and in the debug log I find this:
The Vagrantfile is untouched from my Repo, so I don't think there is a configuration error.
The text was updated successfully, but these errors were encountered: