Issue #5437 has been updated by eric sorenson.

Parent task set to #17017


----------------------------------------
Bug #5437: Manifest errors not reported to clients in 2.6.2
https://projects.puppetlabs.com/issues/5437#change-73802

Author: Ryan Steele
Status: Closed
Priority: High
Assignee: 
Category: error reporting
Target version: 2.6.8
Affected Puppet version: 2.6.2
Keywords: errors passenger 2.6.2
Branch: 


As a preface, we run Ubuntu Server on the amd64 architecture, and use Passenger 
server model.  After upgrading to 2.6.2, it seems manifest errors are no longer 
reported to clients.  For example, this is a catalog run when a typo was made 
in a manifest:


<pre>
root@host:~# puppetd --test --noop
info: Retrieving plugin
info: Loading facts in fai_is_running
info: Loading facts in ipaddress_lan
info: Loading facts in nssldap_ignoreusers
info: Loading facts in fai_is_running
info: Loading facts in ipaddress_lan
info: Loading facts in nssldap_ignoreusers
info: Caching catalog for host.mydomain.com
info: Applying configuration version '1291228811'
notice: Finished catalog run in 0.01 seconds
</pre>

Running with --debug, --no-usecacheonfailure, and --ignorecache made no 
difference and yielded no clues.  It was only after examining the logs on the 
Puppetmaster that I was able to ascertain the problem:

<pre>
Could not render to pson: Could not parse for environment production: Syntax 
error at 'or'; expected ')' at /etc/puppet/manifests/services/openldap.pp:52
</pre>
This worked with the previous release, so I'm guessing it's a new regression, 
though I'm not sure if it's a problem with Puppet or Passenger.



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