Issue #12151 has been updated by John Sellens.

We're still on 2.7.5 so I don't really have a way to test if this is fixed.  I 
will eventually find a way.  Thanks! John

----------------------------------------
Bug #12151: last_run_summary.yaml can be near empty, and not show errors that 
are in last_run_report.yaml
https://projects.puppetlabs.com/issues/12151#change-90917

* Author: John Sellens
* Status: Needs More Information
* Priority: Normal
* Assignee: John Sellens
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
We check the last_run_summary.yaml file (puppet config print lastrunfile) for 
errors. I just noticed a case where last_run_report.yaml says "status: failed" 
and last_run_summary.yaml is effectively empty.  I saw this in 2.7.5.

I had a class that tried to include a non-existent class with include 
"you-should-not-put-funclass-on-this-machine-$hostname" to guard against 
shooting myself in the foot.

Running "puppetd --test" correctly provided this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
not find class you-should-not-put-funclass-on-this-machine-host-example.com for 
host.example.com at 
/etc/puppet-production/modules/funclass/manifests/init.pp:12 on node 
host.example.com

The last_run_report.yaml file showed (and this was reflected in our dashboard) 
the error message, and status: failed.

The last_run_summary.yaml file contained only this:
--- 
  time: 
    last_run: 1327514876

I didn't think that was a very useful summary :-)

Thanks!

John



-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to