Show catalog failures in overview node list

[voxpupuli]

Show catalog failures in overview node list

[corey-hammerton]

When the puppet server experiences errors in the catalog compilation it only logs it and stops. When that happens it does NOT record it in puppetdb and therefore cannot be queried by puppetboard.

[henderb]

I figured that might be the case. Could it show as unreported?

[corey-hammerton]

It will after the time configured in UNRESPONSIVE_HOURS

The process in puppet on runs is

replace facts
replace catalog
store reports

[henderb]

I'll have to test it to make sure, but I've had nodes failing for a day or so and I don't think they were listed. It's set to the default 2 hours.

[henderb]

I think my nodes are using the cached catalog during normal runs, just not when I do puppet agent -tv

[corey-hammerton]

The only way that I've noticed that you can detect this in puppetboard is comparing the timestamps of the catalog and the latest report.

Normally they should be within a few seconds of each other.

[daenney]

Hmmm, that's an interesting theory. Unfortunately I've had the experience of catalog compilations that take well over 5 minutes but if we could define a threshold there it might be worth looking into it.

[gdubicki]

Hey, I would also be happy to see compilation errors in puppetboard. And if I got https://tickets.puppetlabs.com/browse/PDB-16 right and if that info is still up to date, then information about such run actually is pushed to puppetdb, so it can be pulled out by puppetboard. So can we please reopen this ticket?

[bastelfreak]

@gdubicki I reopened the ticket. Are you interested in providing a patch for this?

[gdubicki]

Actually it seems that with latest puppetboard and puppetdb the former does show compilation errors. Sorry for making you think otherwise, @bastelfreak . I think that this issue can be closed as "resolved".

[gdubicki]

I have put results of my verification that it does work in #449.

[gdubicki]

Resolved with ead45c9.