Issue #8973 has been reported by Max Lincoln.

----------------------------------------
Bug #8973: puppet apply not returning usable exit code.
https://projects.puppetlabs.com/issues/8973

Author: Max Lincoln
Status: Unreviewed
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 2.7.1
Keywords: 
Branch: 


Puppet apply is never returning a usable exit code.  This is partly because of 
warnings which appear to be treated as errors.

puppet apply (without --detailed-exitcodes)
  This returns false positives.  It returns 0 even if there is an error running 
the manifest.  It only appears to return an error code if there is a syntax 
error.

puppet apply --detailed-exitcodes
  This is not very usable because successful runs have non-zero returns (0 or 
2).
  It is still not usable with a wrapper because some warnings are treated as 
errors.  This means I am getting a 4 or 6 return code even on successful runs.
  The warning I am seeing is:

/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.1/lib/puppet/provider/service/freebsd.rb:8:
 warning: class variable access from toplevel
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.1/lib/puppet/provider/service/freebsd.rb:9:
 warning: class variable access from toplevel
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.1/lib/puppet/provider/service/freebsd.rb:10:
 warning: class variable access from toplevel
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.1/lib/puppet/provider/service/bsd.rb:11:
 warning: class variable access from toplevel


-- 
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.

Reply via email to