Windows builds on VMWare Workstation failing on 1.1.2 #5622
Comments
|
I reproduced again and captured a more complete log https://gist.github.com/spuder/0b745828383ba390521b67ce4bbc7023 The first time packer tries to restart, it writes 0 bytes to stderr and stdout Every time after that it writes Also strange is that it only tried to restart the system 4 times. In many of the other times I've reproduced this it has tried to restart dozens of times. Even more strange is that packer did not attempt to restart any more times from 9:31 until 10:30. |
SwampDragons
added
builder/vmware
regression
windows-host
windows-guest
and removed
windows-host
labels
|
I also have this problem building Server 1709: Apologies for the additional log prefixes... This is from a CI build under TeamCity. Same situation where the 1h timeout expires without any apparent attempt to retry the connection. The build works just fine on my Linux desktop, which has packer 1.0.4. |
|
@gh2k this failure is also on a linux host? |
|
Yeah, I'm running Gentoo |
|
Can confirm that on my workstation 1.1.1 works, and 1.1.2 doesn't. I'm currently running a |
|
Edit: I'm talking rubbish, sorry.. a739623 is the commit that breaks things, but it's not fixed in Master as I suggested. I did something daft when trying to test that. I managed to get it working in master by pulling |
|
Thanks for going to all the work of that bisect. I made a PR reverting the change you think is the issue: #5672 While still keeping the code that was the main intent of the original PR associated with the bad commit. Can you try that patch out and let me know if it fixes things? |
|
Yep, that works fine, @SwampDragons |
|
Great! |
|
For anyone coming across this using Packer inside Docker - This is also impacting Packer 1.1.2 from a Docker container but going back to 1.1.1 it works fine with windows-restart. |
|
If this is still impacting you in 1.1.3 please open a new ticket. |
|
Works fine in the official Docker image v. 1.1.3 - tried it a few hours ago against a vsphere environment and it worked fine. Thanks! |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Problem
Windows 2012 reboots are not detected properly on packer 1.1.2 with vmware-workstation (linux).
Windows 2012 reboots are detected properly on packer 1.1.2 with vmware-fusion(OsX).
packer 1.0.4 and 1.1.1 work properly on both platforms.
Failures
I have reproduced this over 12 times with 100% consistency. I'm using the same packer definition that has been working for months with 1.0.4
Packer does not fail if using 1.0.4/1.1.1 OR if running 1.1.2 with OSX with vmware-fusion
Successes
Symptom
This is easy, but very time consuming to reproduce, because it only happens after windows 2012 has completed installing windows updates, and then packer attempts to reboot the machine.
Watching the build process, windows always gets stuck shutting down after installing windows updates, and shows error. (Sorry for the picture, the ubuntu build machine doesn't have VNC).
After 5 to 30 minutes, the windows error always clears itself and windows reboots successfully. However packer 1.1.2 never detects that the vm has successfully rebooted, even with a 1 hour timeout.
Installed 1.15.7 of the vmware VIX api library
Workaround
I've had to roll back to 1.0.4 or 1.1.1 to get windows 2012 images working again.
Theories
These are all the milestones from 1.1.2
1.1.2improved scripts after restarts in #5272. Perhaps the check command is too specificWhat other information can I provide to help debug this? I want packer 1.1.2 to work with vmware workstation on linux.
The text was updated successfully, but these errors were encountered: