StefanScherer
commented
10 years ago Afterwards a vagrant provision tst works fine. Then powering on second VM with vagrant up --provider=vcloud a similar problem occurs. This time while looking for rsync in guest:
$ vagrant up --provider=vcloud
Bringing machine 'tst' up with 'vcloud' provider...
Bringing machine 'tst2' up with 'vcloud' provider...
==> tst: VM is already running
==> tst2: Adding VM to existing vApp...
==> tst2: Setting VM hardware...
==> tst2: Powering on VM...
==> tst2: Fixed port collision for 22 => 2222. Now on port 2280.
==> tst2: Fixed port collision for 3389 => 3389. Now on port 2281.
==> tst2: Fixed port collision for 5985 => 55985. Now on port 2282.
==> tst2: Forwarding Ports: VM port 22 -> vShield Edge port 2280
==> tst2: Forwarding Ports: VM port 3389 -> vShield Edge port 2281
==> tst2: Forwarding Ports: VM port 5985 -> vShield Edge port 2282
==> tst2: Waiting for SSH Access on 10.115.4.4:2280 ...
An error occurred executing a remote WinRM command.
Shell: powershell
Command: $command = [Array](Get-Command rsync -errorAction SilentlyContinue)
if ($null -eq $command) { exit 1 }
write-host $command[0].Definition
exit 0
if ($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 0 }
Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2) (http://10.115.4.4:2282)I also think that the rsync lookup is done with winrm, the rsync itself connects with SSH. Is there a better way than rsync for windows guests? Any experiences in the vCloud?
tsugliani
frapposelli
mikecali
Similar to #56, vagrant up may fail while provisioning with winrm communicator a windows guest.
I'm inside my vOrg and so the edge gateway is not configured which also may result in a faster startup as the bridged mode.
First the SSH port of the windows guest will be checked. As there is also a OpenSSH running in my guest, it finally get a connection. Then tries rsync, but rsync is not in path at the moment. I have to fix this. Then the WinRM connection fails, perhaps the WinRM is not up and running as fast as the OpenSSH is. Perhaps a retry loop is also needed here for port 5985.