Anyone have any ideas on this one?

On Wednesday, May 22, 2019 at 2:43:33 PM UTC-4, Justin Metz wrote:
>
> Hi All,
>
> I'm having an intermittent issue producing a consistently working Windows 
> 2012R2 AMI.  It seems that 1 out of every 3 builds produces an AMI that 
> continually throws the message below when an instance created from it is 
> accessed.
>
> (Password not available yet.  Please wait at least 4 minutes after 
> launching an instance before trying to retrieve the auto-generated password)
>
> My assumption is it has something to do with the timing of the call to 
> sysprep, but I have no evidence of that.  I am using the two provisioners 
> below at the end of the config to restart, then kick off the sysprep 
> process, is this correct for 2012R2 in AWS?
> Should I put in a Start-Sleep for a minute or two (in the windows-shell 
> provisioner) before kicking off the sysprep?
>
> I'm curious to find out if anyone else has run into a situation such as 
> this...
>
>        {
>           "type":"windows-restart",
>           "restart_timeout":"30m",
>           "restart_check_command": "powershell -command \"& {Write-Output 
> 'restarted.'}\""
>        },
>        {
>          "type": "windows-shell",
>          "inline": ["\"c:\\Program 
> Files\\Amazon\\Ec2ConfigService\\ec2config.exe\" -sysprep"]
>        }
>
> Thanks in advance!
>
> J
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/63033d6c-9531-405e-a334-a4cc56eb0458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to