Packer not working when setting winrm_password

[bp...@highfive.com]

When creating a Windows AMI on AWS, I am getting stuck at "Waiting for WinRM to become available" when I set winrm_password.

But when I remove winrm_password, it is able to build the AMI. Anyone have an suggestions what might be going on here?

This is what I see in the console:

==> amazon-ebs: Creating temporary keypair: packer_5abd5b4e-51d1-1f2f-ec27-86b7c804c5a9

==> amazon-ebs: Launching a source AWS instance...

==> amazon-ebs: Adding tags to source instance

    amazon-ebs: Adding tag: "Name": "Packer Builder"

    amazon-ebs: Instance ID: i-0dd75cb661ee63bd7

==> amazon-ebs: Waiting for instance (i-0dd75cb661ee63bd7) to become ready...

==> amazon-ebs: Skipping waiting for password since WinRM password set...

==> amazon-ebs: Waiting for WinRM to become available...

Seems weird that winrm_password is causing it to failed.. 

"winrm_password": "TestPassword123!"

[Rickard von Essen]

There is no error in that log. 

--
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 packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/d3b00ef8-319c-4d78-b0be-238cd38762ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bp...@highfive.com]

Sorry, wasn't able to get it, but the error is that it just times out after about 10min. Any idea why it would work without a set password but timeout after setting a password.

[Rickard von Essen]

If you set winrm_password you have to ensure that that pwd is allowed to connect to the VM. When not setting one AWS will set a random one and then Packer reads that. Did you set the password with cloudbase-init? or did the source AMI already have this password baked into it?

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/56d53263-19cc-479f-9ed1-e4a19cf1856e%40googlegroups.com.