I used your snippet below (thank you!) to grab the packer password and
login as the packer user during the point where the build gets stuck. I've
attached a side-by-side screen grab that shows:
- The output where the packer build gets stuck (the debug logs show 401
invalid content, logs in the original post)
- Top has a successful login as the Packer user
- Bottom has a successful login as the domain user
>From what I can tell in the in the logs and screen grab, the domain join
does not initiate a restart. It seems the powershell that joins the domain
returns a lastexitcode of 0. Then gets stuck on the next provisioner which
is the windows-restart (orchestrated via packer).
On Monday, May 13, 2019 at 7:39:22 PM UTC-4, Megan Marsh wrote:
>
> I'd like to validate this for absolute sure. You can use the shell-local
> provisioner to find out the packer password and make sure that you can
> still connect via WinRM using those passwords.
>
> "provisioners": [
> {
> "type": "shell-local",
> "inline": ["echo \"Packer WinRMPassword is {{.WinRMPassword}}\""]
> }
> ]
>
> Does the domain join initiate a restart itself? Packer does a pretty poor
> job of handling restarts that aren't initiated from inside of the restart
> provisioner.
>
--
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/c2f51b2a-7127-4c1c-9440-85a98e860f06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
