Closed tsugliani closed 10 years ago
Hi @StefanScherer
I've tried your Vagrantfile settings for the provisioner, and indeed it fails ... This is really weird and I have no clue why OR what's happening, I also found some similar errors on Google, and they seems to be fixed by some Vagrant patchs.
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"
end
I 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. It's hard to find documentation other than the source code on the internal plugins API for Vagrant.
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.
$ ./vagrantd.sh up
Writing debug log file 06-vagrant-up.log
Calling vagrant up --debug
INFO interface: info: Bringing machine 'web-vm' up with 'vcloud' provider...
INFO interface: info: Bringing machine 'ssh-vm' up with 'vcloud' provider...
INFO interface: info: Building vApp...
INFO interface: info: ==> web-vm: Building vApp...
INFO interface: success: vApp ubuntu1204-stefan-stefans-mac.local-dfc51e18 successfully created.
INFO interface: success: ==> web-vm: vApp ubuntu1204-stefan-stefans-mac.local-dfc51e18 successfully created.
INFO interface: info: Powering on VM...
INFO interface: info: ==> web-vm: Powering on VM...
INFO interface: info: Fixed port collision for 80 => 8080. Now on port 2200.
INFO interface: info: ==> web-vm: Fixed port collision for 80 => 8080. Now on port 2200.
INFO interface: info: Forwarding Ports: VM port 80 -> vShield Edge port 2200
INFO interface: info: ==> web-vm: Forwarding Ports: VM port 80 -> vShield Edge port 2200
INFO interface: info: Forwarding Ports: VM port 22 -> vShield Edge port 2222
INFO interface: info: ==> web-vm: Forwarding Ports: VM port 22 -> vShield Edge port 2222
INFO interface: info: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2200.
INFO interface: info: ==> web-vm: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2200.
INFO interface: info: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2222.
INFO interface: info: ==> web-vm: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2222.
INFO interface: info: Rsyncing folder: /Users/stefan/code/basebox-slave/test/ubuntu1204/ => /vagrant
INFO interface: info: ==> web-vm: Rsyncing folder: /Users/stefan/code/basebox-slave/test/ubuntu1204/ => /vagrant
INFO interface: info: Running provisioner: shell...
INFO interface: info: ==> web-vm: Running provisioner: shell...
INFO interface: detail: Running: /var/folders/lc/ml6r301d1293tvyv3ydn8psr0000gn/T/vagrant-shell20140508-2987-14sb9gh.sh
INFO interface: detail: web-vm: Running: /var/folders/lc/ml6r301d1293tvyv3ydn8psr0000gn/T/vagrant-shell20140508-2987-14sb9gh.sh
INFO interface: info: stdin: is not a tty
INFO interface: info: ==> web-vm: stdin: is not a tty
INFO interface: info: Provisioning web-vm ...
INFO interface: info: ==> web-vm: Provisioning web-vm ...
INFO interface: info: Do a little self-check
INFO interface: info: ==> web-vm: Do a little self-check
INFO interface: info: Running script /tmp/vagrant-shell
INFO interface: info: ==> web-vm: Running script /tmp/vagrant-shell
INFO interface: info: -rwx--x--x 1 vagrant vagrant 236 May 8 14:08 /tmp/vagrant-shell
INFO interface: info: ==> web-vm: -rwx--x--x 1 vagrant vagrant 236 May 8 14:08 /tmp/vagrant-shell
INFO interface: info: Directory /vagrant exists
INFO interface: info: ==> web-vm: Directory /vagrant exists
INFO interface: info: total 2320
INFO interface: info: ==> web-vm: total 2320
INFO interface: info: Adding VM to existing vApp...
INFO interface: info: ==> ssh-vm: Adding VM to existing vApp...
INFO interface: info: Powering on VM...
INFO interface: info: ==> ssh-vm: Powering on VM...
INFO interface: info: Fixed port collision for 80 => 8080. Now on port 2212.
INFO interface: info: ==> ssh-vm: Fixed port collision for 80 => 8080. Now on port 2212.
INFO interface: info: Fixed port collision for 22 => 2222. Now on port 2213.
INFO interface: info: ==> ssh-vm: Fixed port collision for 22 => 2222. Now on port 2213.
INFO interface: info: Forwarding Ports: VM port 80 -> vShield Edge port 2212
INFO interface: info: ==> ssh-vm: Forwarding Ports: VM port 80 -> vShield Edge port 2212
INFO interface: info: Forwarding Ports: VM port 22 -> vShield Edge port 2213
INFO interface: info: ==> ssh-vm: Forwarding Ports: VM port 22 -> vShield Edge port 2213
INFO interface: info: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2212.
INFO interface: info: ==> ssh-vm: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2212.
INFO interface: info: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2213.
INFO interface: info: ==> ssh-vm: Creating NAT rules on [SS-EDGE] for IP [10.100.50.4] port 2213.
Vagrant exited with 1. See 06-vagrant-up.log for more details
This is the rest of the debug output:
DEBUG read_ssh_info: Getting port forwarding rules...
"SEND GET https://roecloud001/api/vApp/vapp-5f712074-94ec-4a89-8665-6668e288fa65/networkConfigSection"
"RECV 200"
<?xml version="1.0" encoding="UTF-8"?>
<NetworkConfigSection xmlns="http://www.vmware.com/vcloud/v1.5" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" type="application/vnd.vmware.vcloud.networkConfigSection+xml" href="https://roecloud001/api/vApp/vapp-5f712074-94ec-4a89-8665-6668e288fa65/networkConfigSection/" ovf:required="false" xsi:schemaLocation="http://schemas.dmtf.org/ovf/envelope/1 http://schemas.dmtf.org/ovf/envelope/1/dsp8023_1.1.0.xsd http://www.vmware.com/vcloud/v1.5 http://roecloud001/api/v1.5/schema/master.xsd">
<ovf:Info>The configuration parameters for logical networks</ovf:Info>
<Link rel="edit" type="application/vnd.vmware.vcloud.networkConfigSection+xml" href="https://roecloud001/api/vApp/vapp-5f712074-94ec-4a89-8665-6668e288fa65/networkConfigSection/"/>
<NetworkConfig networkName="Vagrant-vApp-Net">
<Link rel="repair" href="https://roecloud001/api/admin/network/89c42abc-060e-47ec-8fef-abdfcde93502/action/reset"/>
<Link rel="syncSyslogSettings" type="application/vnd.vmware.vcloud.task+xml" href="https://roecloud001/api/admin/network/89c42abc-060e-47ec-8fef-abdfcde93502/action/syncSyslogServerSettings"/>
<Description/>
<Configuration>
<IpScopes>
<IpScope>
<IsInherited>false</IsInherited>
<Gateway>172.16.32.113</Gateway>
<Netmask>255.255.255.240</Netmask>
<Dns1>8.8.8.8</Dns1>
<Dns2>8.8.4.4</Dns2>
<IsEnabled>true</IsEnabled>
<IpRanges>
<IpRange>
<StartAddress>172.16.32.114</StartAddress>
<EndAddress>172.16.32.126</EndAddress>
</IpRange>
</IpRanges>
<AllocatedIpAddresses>
<IpAddress>172.16.32.115</IpAddress>
<IpAddress>172.16.32.113</IpAddress>
<IpAddress>172.16.32.114</IpAddress>
</AllocatedIpAddresses>
</IpScope>
</IpScopes>
<ParentNetwork name="SS-INTERNAL" id="3fd7a97b-b182-41a0-8df5-3b67b5c08b27" href="https://roecloud001/api/admin/network/3fd7a97b-b182-41a0-8df5-3b67b5c08b27"/>
<FenceMode>natRouted</FenceMode>
<RetainNetInfoAcrossDeployments>false</RetainNetInfoAcrossDeployments>
<Features>
<FirewallService>
<IsEnabled>false</IsEnabled>
<DefaultAction>drop</DefaultAction>
<LogDefaultAction>false</LogDefaultAction>
</FirewallService>
<NatService>
<IsEnabled>true</IsEnabled>
<NatType>portForwarding</NatType>
<Policy>allowTraffic</Policy>
<NatRule>
<Id>65537</Id>
<VmRule>
<ExternalIpAddress>10.115.4.6</ExternalIpAddress>
<ExternalPort>2212</ExternalPort>
<VAppScopedVmId>0a327f6f-c79f-4048-aee9-c2993bb4b308</VAppScopedVmId>
<VmNicId>0</VmNicId>
<InternalPort>80</InternalPort>
<Protocol>TCP</Protocol>
</VmRule>
</NatRule>
<NatRule>
<Id>65538</Id>
<VmRule>
<ExternalIpAddress>10.115.4.6</ExternalIpAddress>
<ExternalPort>2213</ExternalPort>
<VAppScopedVmId>0a327f6f-c79f-4048-aee9-c2993bb4b308</VAppScopedVmId>
<VmNicId>0</VmNicId>
<InternalPort>22</InternalPort>
<Protocol>TCP</Protocol>
</VmRule>
</NatRule>
<NatRule>
<Id>65539</Id>
<VmRule>
<ExternalIpAddress>10.115.4.6</ExternalIpAddress>
<ExternalPort>2200</ExternalPort>
<VAppScopedVmId>b793dfbd-c44c-4e29-972b-bf78a04cb9e9</VAppScopedVmId>
<VmNicId>0</VmNicId>
<InternalPort>80</InternalPort>
<Protocol>TCP</Protocol>
</VmRule>
</NatRule>
<NatRule>
<Id>65540</Id>
<VmRule>
<ExternalIpAddress>10.115.4.6</ExternalIpAddress>
<ExternalPort>2222</ExternalPort>
<VAppScopedVmId>b793dfbd-c44c-4e29-972b-bf78a04cb9e9</VAppScopedVmId>
<VmNicId>0</VmNicId>
<InternalPort>22</InternalPort>
<Protocol>TCP</Protocol>
</VmRule>
</NatRule>
</NatService>
</Features>
<SyslogServerSettings/>
<RouterInfo>
<ExternalIp>10.115.4.6</ExternalIp>
</RouterInfo>
</Configuration>
<IsDeployed>true</IsDeployed>
</NetworkConfig>
</NetworkConfigSection>
DEBUG read_ssh_info: We're running vagrant behind an Organization vDC
edge
INFO warden: Calling OUT action: #<VagrantPlugins::VCloud::Action::ReadSSHInfo:0x00000100dea890>
INFO warden: Calling OUT action: #<VagrantPlugins::VCloud::Action::ConnectVCloud:0x00000100d8a558>
DEBUG ssh: Checking key permissions: /Users/stefan/.vagrant.d/insecure_private_key
INFO ssh: Attempting SSH connnection...
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: 10.100.50.4
INFO ssh: - Port: 2213
INFO ssh: - Username: vagrant
INFO ssh: - Password? false
INFO ssh: - Key Path: ["/Users/stefan/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2014-05-08T23:10:39.144527 #2987] DEBUG -- net.ssh.transport.session[80b2a5e0]: establishing connection to 10.100.50.4:2213
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO retryable: Retryable exception raised: #<Errno::ENETUNREACH: Network is unreachable - connect(2)>
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: 10.100.50.4
INFO ssh: - Port: 2213
INFO ssh: - Username: vagrant
INFO ssh: - Password? false
INFO ssh: - Key Path: ["/Users/stefan/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2014-05-08T23:10:42.269478 #2987] DEBUG -- net.ssh.transport.session[80b805f8]: establishing connection to 10.100.50.4:2213
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO retryable: Retryable exception raised: #<Errno::ENETUNREACH: Network is unreachable - connect(2)>
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: 10.100.50.4
INFO ssh: - Port: 2213
INFO ssh: - Username: vagrant
INFO ssh: - Password? false
INFO ssh: - Key Path: ["/Users/stefan/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2014-05-08T23:10:45.340393 #2987] DEBUG -- net.ssh.transport.session[820bfd88]: establishing connection to 10.100.50.4:2213
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO retryable: Retryable exception raised: #<Errno::ENETUNREACH: Network is unreachable - connect(2)>
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: 10.100.50.4
INFO ssh: - Port: 2213
INFO ssh: - Username: vagrant
INFO ssh: - Password? false
INFO ssh: - Key Path: ["/Users/stefan/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2014-05-08T23:10:48.413210 #2987] DEBUG -- net.ssh.transport.session[820d7e38]: establishing connection to 10.100.50.4:2213
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO retryable: Retryable exception raised: #<Errno::ENETUNREACH: Network is unreachable - connect(2)>
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: 10.100.50.4
INFO ssh: - Port: 2213
INFO ssh: - Username: vagrant
INFO ssh: - Password? false
INFO ssh: - Key Path: ["/Users/stefan/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2014-05-08T23:10:51.484713 #2987] DEBUG -- net.ssh.transport.session[820f72d8]: establishing connection to 10.100.50.4:2213
DEBUG ssh: == Net-SSH connection debug-level log END ==
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000100c89640>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001041067d8>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000010520bbf0>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Network is unreachable - connect(2)
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock: machine-action-3691848877293461b6e453faa5aa1c52
INFO environment: Running hook: environment_unload
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000104209860>
/Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh/transport/session.rb:70:in `initialize': Network is unreachable - connect(2) (Errno::ENETUNREACH)
from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh/transport/session.rb:70:in `open'
from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh/transport/session.rb:70:in `block in initialize'
from /Applications/Vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
from /Applications/Vagrant/embedded/lib/ruby/2.0.0/timeout.rb:97:in `timeout'
from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh/transport/session.rb:67:in `initialize'
from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh.rb:202:in `new'
from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.0/lib/net/ssh.rb:202:in `start'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/plugins/communicators/ssh/communicator.rb:352:in `block (2 levels) in connect'
from /Applications/Vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/plugins/communicators/ssh/communicator.rb:331:in `block in connect'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/util/retryable.rb:17:in `retryable'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/plugins/communicators/ssh/communicator.rb:330:in `connect'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/plugins/communicators/ssh/communicator.rb:179:in `execute'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/sync_folders.rb:54:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/provision.rb:80:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/forward_ports.rb:22:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/handle_nat_port_collisions.rb:145:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/call.rb:53:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/power_on.rb:21:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/build_vapp.rb:221:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/call.rb:53:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/inventory_check.rb:15:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Users/stefan/.vagrant.d/gems/gems/vagrant-vcloud-0.3.1/lib/vagrant-vcloud/action/connect_vcloud.rb:51:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/call.rb:53:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/machine.rb:190:in `action_raw'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/machine.rb:167:in `block in action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/environment.rb:423:in `lock'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/machine.rb:155:in `action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
Hi @StefanScherer
Hmm, can you give it another try, as I see it's a network problem from this line:
INFO retryable: Retryable exception raised: #<Errno::ENETUNREACH: Network is unreachable - connect(2)>
I did try it with your Vagrantfile settings on my setup and 3 VMs and it seems fine. You might want to clear the environment, and maybe Redeploy the Edge Gateway in vCloud Director if this error persists.
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. Seems to do the job. Tested with Vagrant 1.6.1.
@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.