Getting the catalog even if the puppet fails

[Abhijeet R]

Hi,

I have a situation where loading of facts & caching for catalog is done.
After that, the puppet fails with an error.

1.
info: Caching catalog for my.domain.com
2.
No title provided and "Nagios3::Host[]" is not a valid resource
reference

Now, the thing is, in my /var/lib/puppet/client_yaml/catalog, the yaml
file is old. May be, puppet updates it only after there is a successful
run. If I could have a look at the catalog, may be I could debug this.

Is there a place where this catalog is created temporarily or is it
in-memory? Is there any to way to get the catalog?

The puppet version being used is: 2.6.13.

--
Regards,
Abhijeet
http://blog.abhijeetr.com

[jcbollinger]

On Thursday, October 11, 2012 11:48:29 PM UTC-5, Abhijeet Rastogi wrote:

Hi,

I have a situation where loading of facts & caching for catalog is done.
After that, the puppet fails with an error.

 1.
    info: Caching catalog for my.domain.com
 2.
    No title provided and "Nagios3::Host[]" is not a valid resource
    reference

That certainly looks strange.  You say that is the result of Puppet trying to apply a catalog it successfully retrieved from the master?
 

Now, the thing is, in my /var/lib/puppet/client_yaml/catalog, the yaml
file is old. May be, puppet updates it only after there is a successful
run. If I could have a look at the catalog, may be I could debug this.

Is there a place where this catalog is created temporarily or is it
in-memory? Is there any to way to get the catalog?

I'm not sure, but it might make sense that Puppet would not write the catalog to disk until it verifies it by successful application.
 

The puppet version being used is: 2.6.13.

Are you certain that the client and the master both run that version?  In particular, is there any chance that the client is running a newer version than the master?  That would be my best guess for how the client might reject a catalog that the master compiled successfully.


John

[Abhijeet Rastogi]

Hi John,

So, it turns out that some other guy pushed the wrong CSV in extdata, It had a trailing ",". Because of that, a resource with no title was getting created. Poor me, I should have gone that far before posting here. Thanks anyways.

Cheers,
Abhijeet