adjackura
commented
6 years ago The change you mention wont impact you as you are running with the -noshutdown flag. It appears as though sysrep.exe is hanging for some reason, this is usually because of some issue with the OS like a previously failed sysprep run (this is all Windows sysprep and shouldn't have anything to do with the GCE specific wrapping code) C:\Windows\Panther\setupact.log wont tell you much as that is from the instance startup, for the list of logs see: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs You should take a look at c:\System32\Sysprep\Panther, that should show logs from the sysprep generalize run.
petemounce
lmayorga1980
I'm not sure if this is the same issue as #154, but I have GCESysprep on Windows 2016 (image
windows-server-2016-dc-v20180814) hung, apparently, while running sysprep.exe. I'm wondering whether I should continue waiting (~3 hours and counting), or write it off.Edit: I elected to hit
Stopin the cloud console; packer has treated that as a success and captured the image, but when I remote into an instance from it I'm presented with the "shutdown event tracker" helpfully asking me whether that was unplanned or not, andwindeploywas not run, so I think this is not a clean end result.Packer-side Logs (also visible via serial port):
Triggered via packer provisioner (using
-noshutdownbecause I need packer to manage the lifetime of the instance, otherwise it will treat the shutdown as an instance-death and fail the build):Using sysinternals process explorer I can see that the process is alive; it's
"C:\Windows\System32\Sysprep\sysprep.exe" /generalize /oobe /quit "/unattend:C:\Program Files\Google\Compute Engine\sysprep\unattended.xml". I have not customised the unattended.xml.I can see that the image that I'm building (from the
windows-2016image family does not yet have @adjackura's change from 62223fe08b9fbb080b034aa09c4cfc138c8ba080 within it, yet - I took a look at thesysprep.ps1and it lacks the/fflag - though the process itself has not executed to that point so far.Inside
C:\Windows\Panther\setupact.log(80KB, no longer growing) the last few lines are as follows. There are noErrorlevel log lines. There are a few warnings, 2nd block. There's 0KB insidesetuperr.log, but I don't know whether there are some lines pending being flushed by something.Last few lines:
Warning occurences:
I am naively suspicious of
2018-09-11 10:12:41, Warning [0x06036c] IBS Callback_SystemRestore: Failed to set System Restore state. GLE is [126]in that while I'm definitely not very familiar with sysprep, those sound like oddities.
Finally, inside
sysprep.ps1I can see the snippet:The log line suggests that it expects the
Invoke-ExternalCommandcmdlet to be async, but by observation it is not. Is that an error in the intended behaviour, or the wording of the log message, or am I reading into it too much? When I have run non-powershell things from powershell, I think I've usually usedStart-Process <path> <args> -wait -passthru- but I'm not a powershell expert, and I'm unfamiliar with the technique being used inside of https://github.com/GoogleCloudPlatform/compute-image-windows/blob/master/gce_base.psm1#L333 to know whether it will stream or wait until the command is done before giving any output.Are there any other things I could provide to you, or try out, to see whether I can get a working sysprep?