Jira (PUP-1929) puppet apply should not return 0 if catalog compilation fails

[Michael Prokop (JIRA)]

Title: Message Title

Michael Prokop commented on an issue   Re: puppet apply should not return 0 if catalog compilation fails Same here with puppet 2.7.23 (Debian/wheezy), also without '--detailed-exitcodes': # puppet agent --test info: Caching catalog for jenkins-dev info: Applying configuration version '1398338846' err: Could not apply complete catalog: Found 1 dependency cycle: (File[<snip>] => Class[Jenkins::Ec2tools] => Class[Jenkins::Ssh] => <snip>) Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz notice: Finished catalog run in 0.39 seconds # echo $? 0 It's quite dangerous and misleading because even in puppet dashboard you don't notice that a host running into such a problem doesn't receive any updates. Add Comment   Puppet / PUP-1929 puppet apply should not return 0 if catalog compilation fails When using the --detailed-exitcodes option, and preforming the following: {code} bundle exec puppet apply --detailed-exitcodes -e 'notify { "foo": require => Notify[foo] }' /dev/mem: Permission denied Notice: Compiled catalog for blah in environment production in 0.04 seconds /dev/mem: Permission denied Error: Could not apply complete catalog: Fo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.