Issue #14055 has been updated by Nan Liu.
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. ---------------------------------------- Bug #14055: Windows packages should ignore exit code 3010 https://projects.puppetlabs.com/issues/14055#change-64223 Author: Wouter verhelst Status: Accepted Priority: Normal Assignee: Josh Cooper Category: windows Target version: 2.7.x Affected Puppet version: 2.7.13 Keywords: windows msi reboot Branch: Hi, 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. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
