Sometimes the openssh.bat errors and doesn't properly configure SSH about packer-windows HOT 13 CLOSED

I've not seen this myself. Please post any output you can when it happens again.

from packer-windows.

Is it possible that it's not a race condition, but rather an error installing OpenSSH (https://github.com/joefitzgerald/packer-windows/blob/master/scripts/openssh.bat#L4) which results in the files not existing?

It seems like we could capture this if we ensured OpenSSH installation produces a log?

from packer-windows.

It possible that it failed to download some of the times, but there's definitely more too it than that. I've seen it install OpenSSH fine, but then complain it cannot find the config files.

It becomes very easy to reproduce this when you replace the batch file with this powershell script. This is because it either runs faster since its a single powershell process or because powershell isn't waiting for the install command to finish. The commented out sleep is required in order to get the script to run successfully.

from packer-windows.

Thanks for sharing this, I'll check it out.

from packer-windows.

@sneal sounds like we should use your script, and increase the sleep to 15 seconds to be safe. Strange behavior, but anything's possible with a Nullsoft installer ;)

Want to make a pull request for that?

from packer-windows.

... And by pull request I mean... just commit the changes and push them in the develop branch ;) (By the way, we've switched to using git flow for this repo)...

from packer-windows.

sure, np

from packer-windows.

It works great for me running the installer like this

Start-Process "C:\Windows\Temp\openssh.exe" "/S /port=22 /privsep=1 /password=D@rj33l1ng" -NoNewWindow -Wait

@sneal, can you verify?

from packer-windows.

That makes sense - in general, you would want any installer that is launched to be run synchronously, by waiting for the PowerShell process to exit.

from packer-windows.

I've pushed 70ac237 which I can verify works pretty well here (win 2012 vmware/virtualbox).

I did convert the otherwise elegant...

$env:PATH > c:\windows\temp\PATH

to

Set-Content C:\Windows\Temp\PATH ([byte[]][char[]] $env:PATH) -Encoding Byte

...in order to prevent the automatic carriage-returns because Powershell is so darn helpful. PATH management in general has been the worst thing ever.

from packer-windows.

Nice, thanks Dylan!

On Saturday, December 7, 2013, Dylan Meissner wrote:

I've pushed 70ac23770ac2370ae9772c3068487d64183be35fb3e40cawhich I can verify works pretty well here (win 2012 vmware/virtualbox).

I did convert the otherwise elegant...

$env:PATH > c:\windows\temp\PATH

to

Set-Content C:\Windows\Temp\PATH ([byte[]][char[]] $env:PATH) -Encoding Byte

...in order to prevent the automatic carriage-returns because Powershell
is so darn helpful. PATH management in general has been the worst thing
ever.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-30064183
.

from packer-windows.

You bet. Thanks for the fine script. Let us know how it works out.

from packer-windows.

This has now been released in v1.3

from packer-windows.