You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Overview of the Issue
Occasionally, Packer skips certain steps during the Windows image build process. Based on my yesterday tests, this occurs approximately once every 10 runs. In that case, Packer skipped the Windows Update step and one of three PowerShell scripts (script-3.ps1, but that also seems to be random). Despite these omissions, Packer does not provide any indication that the image is incomplete — the build still completes successfully. Additionally, the faulty run was significantly shorter (~15 minutes) compared to a proper run (~30 minutes).
Reproduction Steps
Build Windows image using similar template multiple times, search for incomplete image and shorter build time.
Community Note
Overview of the Issue
Occasionally, Packer skips certain steps during the Windows image build process. Based on my yesterday tests, this occurs approximately once every 10 runs. In that case, Packer skipped the Windows Update step and one of three PowerShell scripts (
script-3.ps1
, but that also seems to be random). Despite these omissions, Packer does not provide any indication that the image is incomplete — the build still completes successfully. Additionally, the faulty run was significantly shorter (~15 minutes) compared to a proper run (~30 minutes).Reproduction Steps
Build Windows image using similar template multiple times, search for incomplete image and shorter build time.
Packer version
1.12.0
Simplified Packer Template
All scripts contain
$ErrorActionPreference = 'Stop';
at the very beginning.Operating system and Environment details
Ubuntu 24
Log Fragments and crash.log files
Logs with
PACKER_LOG=1
option. I've compared proper and faulty run logs line by line, and pasted here only the differences.Windows update
Faulty run
Proper run
Script-3.ps1 execution
Faulty run
Proper run
The text was updated successfully, but these errors were encountered: