The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Windows packages should ignore exit code 3010
|Assignee:||Josh Cooper||% Done:|
|Affected Puppet version:||2.7.13||Branch:||https://github.com/puppetlabs/puppet/pull/851|
|Keywords:||windows msi reboot|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
I’ve been trying out puppet to manage some Windows machines. Installing MSI packages works most of the time, but in some cases an MSI will exit with exit state “3010”.
A quick google search revealed that this exit state means “installation was successful, reboot pending”. Unfortunately, puppet does not seem to know this, and marks the installation as failed, resulting in it being retried on every puppet run.
It might be good if puppet ignored that exit state, so that the installation would at least be marked as done.
#2 Updated by Nan Liu about 3 years ago
I’m running into the same issue with DISM: https://github.com/puppetlabs/puppetlabs-dism/issues/4
The issue I’m struggling with, is depending whether the system have pending reboot, this can trigger other exit code depending on whether the installer cares or not. For example when I run vCenter installer, the exit code is 67 when pending reboot. In this case, would it be better if we check for the registry key and simply skip the install process and say reboot pending? I can see potential issues with multi-step install process that requires reboot, so not sure what’s the best solution here.
#4 Updated by Josh Cooper about 3 years ago
- Status changed from In Topic Branch Pending Review to Merged - Pending Release
- Target version changed from 2.7.x to 2.7.18