Closed vishagilityroots closed 7 years ago
If you look at the error
Guest path: /tmp/vagrant-puppet/manifests-aa0e7a61aebfb30adf6effefa1b25cdc
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "-e" "ssh -p 22 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/tmp/ssh.248 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/home/vagrant/.vagrant.d/insecure_private_key'" "--exclude" ".vagrant/" "/work/agilityroots/biztalk-provisioner/provisioning/environments/production/manifests/" "vagrant@ec2-13-126-91-144.ap-south-1.compute.amazonaws.com:/tmp/vagrant-puppet/manifests-aa0e7a61aebfb30adf6effefa1b25cdc"
Error: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
This error occurred on Cygwin; the paths are cygwin-specific and will not work on the Windows host. It appears I may have encountered https://github.com/mitchellh/vagrant/issues/6702.
There are lots of comments in that issue that say Cygwin is not a good choice for Windows provisioning. I tried moving to cmd.exe
.
This should already be fixed by #5 .
During provisioning phase, the Vagrant box needs to rsync several folders to the remote machine. The remote directory does appear to get created but it fails unexpectedly.