[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-06 Thread jcbollinger
On Thursday, December 6, 2012 5:14:51 AM UTC-6, Luca Gioppo wrote: > > OK I'm getting mad. > > All of a sudden after a few mods I received this error from the > puppet_master. > > I reverted all the changes done up to a last working set but no prize > still this error and I cannot understand wh

[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-06 Thread Luca Gioppo
Ruby version 1.8.7 on both master and agent. But on the agent I get: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: can't instantiate uninitialized class Debug: Using cached catalog for jbossm.cortile.cloudlabcsi.local Using cached catalog So the problem should be in

[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-07 Thread Luca Gioppo
Anyone has a good hint on how to get better debug info on this problem? Other nodes work correctly so puppet master is not broken just the catalog of the node I'm working on, but cannot manage to find the bug. Luca Il giorno giovedì 6 dicembre 2012 12:14:51 UTC+1, Luca Gioppo ha scritto: > > OK I

[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-07 Thread jcbollinger
On Thursday, December 6, 2012 9:28:29 AM UTC-6, Luca Gioppo wrote: > > Ruby version 1.8.7 on both master and agent. > > But on the agent I get: > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > can't instantiate uninitialized class > Debug: Using cached catalog for j

[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-10 Thread Luca Gioppo
No the behaviour has been always the same: On the server I get: Compiled catalog for jbossm.cortile.cloudlabcsi. local in environment production in 1.53 seconds Info: Caching catalog for jbossm.cortile.cloudlabcsi.local Debug: Searched for resources in 0.01 seconds Error: can't instantiate uniniti

[Puppet Users] Re: Error: can't instantiate uninitialized class

2012-12-10 Thread jcbollinger
On Monday, December 10, 2012 8:22:25 AM UTC-6, Luca Gioppo wrote: > > No the behaviour has been always the same: > Ok. > > It colud be a template??? I'll check it, but have no clue. > Yes. Templates can execute arbitrary Ruby code, so they can trigger any error that Ruby can throw. Wheth