Hello John, from a puppet-beginners point of view it seems astonishing that running "puppet agent -t" on node A can have influence on the catalog prepared for node B.
I agree that your inital response perfectly fitted to the solution of the problem. Thanks for that explanation! Kind regards Helmut Am Mittwoch, 13. August 2014 17:53:20 UTC+2 schrieb jcbollinger: > > Hello Helmut, > > I am glad you have resolved your issue. > > I have recently been travelling, and hence not responsive to this list, > but I feel compelled to observe that the problem turned out to be exactly > what I said in my initial response it might be: "In particular, I am > inclined to guess that one or more of your manifests [...] has some > top-scope declarations that are neither class nor type definitions." That > response goes on to explain why having such declarations is a problem. > > I can also be more specific now, since it seems you may be tripping over > the semantics of the 'include' statement. It is essential to understand > that 'include' directs Puppet that the designated class must be included in > the catalog being constructed -- NOT to interpolate any additional DSL code > into the manifest file in which it appears. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e0f1952b-f01f-47f3-87a7-4d8c8bef3202%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
