On Friday, September 28, 2012 7:44:02 AM UTC-5, Axel Bock wrote: > > Okay, I am one step farther. > > After seeing "Invalid resource" for about 100 times I symlinked the type > and provider dirs to /var/.../puppet/ (the global, core putty installation > files). > I basically wanted to see if I have an invalid ruby file, or if puppet > simply doesn't notice the downloaded plugins. > > It turns out - the latter. in the global puppet dir I get no more "Invalid > type" errors, and my debug print statement in the exists? method gets > printed. > > Now - what do I have to do to make puppet realize that this stupid plugin > is there? It _does_ even autoload it - if I change it I get a diff printed, > the code gets executed (I see print statements I put in there) - but once > the type shall be acutally used puppet chickens out. This is so extremely > annoying. > > Pluginsync = true is activated in the [main] and [master] section of > client and master. > > > Does nobody have any idea? I am using puppet 2.6.17 from the SuSE SLES 11 > SP2 repo. > >> >>> This is standard behavior. The master does not load types or providers directly from modules. If it is its own client then it will sync them to itself when the agent runs, or else you can copy them into position manually. Under some circumstances you will need to restart the master after the type and provider are synced, though I thought that was mostly when you modify an existing type / provider.
John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Iojb7yC_FfgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
