[PUP-8461] When installing or upgrading an EXE package on Windows Puppet ignores its exit code Created: 2017/10/30 Updated: 2018/02/13
|Affects Version/s:||PUP 4.10.7|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Windows Server 2012 R2
|Method Found:||Needs Assessment|
|QA Risk Assessment:||Needs Assessment|
Puppet's way of launching the installer
cmd.exe /c start /w install.exe
ignores the exit code of the installer and returns the exit code of cmd.exe instead
|Comment by Josh Cooper [ 2018/02/12 ]|
Momtchil Momtchev Can you provide more information about what exit code install.exe is returning and why that isn't being captured correctly? For example, we currently handle reboot related exit codes 1641 and 3010.
|Comment by Momtchil Momtchev [ 2018/02/13 ]|
No matter what the installer returns, Puppet considers that the installation was successful and will proceed with installing its dependencies.
I don't work for that customer anymore, but from what I remember it was an 8bit non-zero code.
You can easily reproduce it by running another GUI program that way (cmd /c /w start), the return code will be that of cmd.exe.