Issue #11984 has been updated by Daniel Pittman. Target version deleted (2.7.x)
---------------------------------------- Bug #11984: improperly configured storeconfigs do not return valuable exit codes https://projects.puppetlabs.com/issues/11984 Author: Justin Stoller Status: Accepted Priority: Normal Assignee: Category: stored configuration Target version: Affected Puppet version: 2.7.9 Keywords: exit codes, storeconfigs Branch: Noticed this while writing tests: <pre> root@ubuntu-beta:~# puppet --version 2.7.9 root@ubuntu-beta:~# puppet apply --detailed-exitcodes -e '@@notify { "$hostname": tag => "storeconfgs" }' warning: You cannot collect without storeconfigs being set on line 1 notice: Finished catalog run in 0.03 seconds root@ubuntu-beta:~# echo $? 0 </pre> as well as <pre> root@ubuntu-beta:~# puppet apply --detailed-exitcodes -e "Notify <<| tag == 'storeconfig_test' |>>" warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 1 warning: Not collecting exported resources without storeconfigs notice: Finished catalog run in 0.03 seconds root@ubuntu-beta:~# echo $? 0 </pre> checking <pre> * --detailed-exitcodes: Provide transaction information via exit codes. If this is enabled, an exit code of '2' means there were changes, an exit code of '4' means there were failures during the transaction, and an exit code of '6' means there were both changes and failures. </pre> >From reading this I was expecting, if not a 1, at least a 4 as the exit code. -- 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.
