Issue #22250 has been updated by Andrew Parker. Status changed from In Topic Branch Pending Review to Merged - Pending Release
Merged into master in <https://github.com/puppetlabs/puppet/commit/dce2f6118089896f4853b618e5908671db662caf>. ---------------------------------------- Bug #22250: Reports are inconsistent in the way they expose failures https://projects.puppetlabs.com/issues/22250#change-96775 * Author: Kylo Ginsberg * Status: Merged - Pending Release * Priority: Normal * Assignee: Kylo Ginsberg * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1845 ---------------------------------------- Generally a failure in a puppet run will generate a report including a Puppet::Resource::Status with failed=true and the events array including an explanatory event. However, it is possible to have a failure where failed=true but the events array is empty. This can be reproduced with the following manifest snippet: <pre><code class="ruby"> package {"does_not_exist": ensure => present } service { "does_not_exist": provider => init, ensure => running } </code></pre> NOTE: we've tested this same scenario with the launchd provider for service, and it correctly generates the event as expected. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
