I think PR 5593 <https://github.com/mitchellh/vagrant/pull/5593> should fix 
your issue.

I think what happened is that we tightened up the error code and stderr 
detection in the WinRM communicator and this exposed an issue with the Salt 
bootstrap PowerShell script 
<https://github.com/mitchellh/vagrant/blob/master/plugins/provisioners/salt/bootstrap-salt.ps1>.
 
Basically, the script is not idempotent. It attempts to create a directory 
that can already exists, and if it does exist it causes an error.

You might be able to workaround the issue by providing your own salt 
bootstrap script to the provisioner block.

On Monday, April 13, 2015 at 8:30:23 AM UTC-7, Oliver Bestwalter wrote:
>
> Hi,
>
> On Monday, 13 April 2015 17:19:07 UTC+2, dragon788 wrote:
>>
>> It sounds like its seeing a port already in use and trying to recover 
>> that, but it looks like you have mixed slashes in the powershell.exe 
>> command, mixed slashes are BAD. Try making them all / or all \ in the path 
>> to your script.
>>
>>
>  Thanks, but I don't think this has anything to do with the problem as far 
> as I understand it: 
>
> > New-Item : Item with specified name C:\tmp\ already exists.
>
> If I understand that correctly it complains that the folder already exists 
> - so this has nothing to do with ports - correct?
>
> As for the mixing of backslashes and slashes: That is ugly - I agree, but 
> it's not a problem, see for example here
>
> > winrm: Uploading: 
> /home/obestwalter/work/prodenv/vagrant_winbox/salt/minion to C:\tmp/minion
>
> that happens all over the place and is not under my control. I am 
> developing mainly on linux and I used to wonder if this mixing is a problem 
> on windows, so I made some experiments a while ago with paths with mixed 
> slashes and my conclusion was, that windows does not really care ...
>
> Cheers
> Oliver
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to