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:
--detailed-exitcodes docs should mention that exitcode is a bitmask
|Assignee:||Nick Fagerlund||% Done:|
|Affected Puppet version:||2.7.1||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
When running the agent with —detailed-exitcodes, I noticed it exited with status 6 to indicate that (a) there were changes and (b) some of those changes failed.
It’d be nice if the docs mentioned this bitmask treatment; changing the —detailed-exitcodes docs to something like this:
Provide transaction information via the exit code, which is a bitmask. An exit code of ‘2’ means there were changes, an exit code of ‘4’ means that there were failures during the transaction, and an exit code of ‘6’ (both the 2 and 4 bits set) means that there were both changes and failures during the transaction.
#2 Updated by Nick Fagerlund about 4 years ago
- Status changed from Accepted to Merged - Pending Release
References to the
--detailed-exitcodes flag in the agent, apply, and device man pages have been updated in the 2.7.x branch. Since we’re in an RC right now, the updated documentation should appear in 2.7.3.