Hi Dan, yes - you were right, had I not been wrong before. That's a copy and paste error of the post actually. The module is in fact called "reposync", the file name as well as the module itself inside.
Sorry, and thanks very much for your help. Greetings, Axel. Am Montag, 8. Oktober 2012 18:37:13 UTC+2 schrieb Dan Bode: > > > > On Mon, Oct 8, 2012 at 7:56 AM, Axel B <[email protected] > <javascript:>>wrote: > >> Hello readers, >> >> I have already asked this question in Puppet Users, but so far without >> working solution. Maybe I have more luck in here :) . I have developed a >> custom SVN type (based on http://is.gd/W0cIMS among others), and I guess >> it's fairly correct ruby code. (at least I don't get any syntax errors). >> Now I have deployed it in my module in <module>/lib/puppet/type/repo_** >> checkout.rb and <module>/lib/puppet/provider/**repo_checkout/svn.rb, and >> the files do get transferred to the client. >> >> in my site.pp I do the following: >> >> repo_checkout { "test" : >> source => "svn://l1214022/puppet/trunk/**bas3_bali", >> method => "export", >> path => "/home/rsync/puppet/checkthis"**, >> } >> >> ... and I get the following error: >> >> err: Could not retrieve catalog from remote server: Error 400 on SERVER: >> Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid >> resource type reposync at /etc/puppet/manifests/site.pp:**98 on node ... >> > > This is an error on the master. It looks like you are trying to refer to a > resource named reposync in the manifest (at the indicated line) and your > resource is named repo_checkout > > >> >> >> If I insert print statements in the code and invoke puppet agent --debug, >> I see the statements being executed on the client: >> >> info: Loading downloaded plugin /home/rsync/.puppet/var/lib/** >> puppet/type/reposync.rb >> *lala Huhu *debug: catalog supports formats: b64_zlib_yaml dot pson raw >> yaml; using pson >> >> Directly afterwards I get to see the message "Invalid resource type ...". >> It loads, updates, but does not find. After seeing this message 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 on screen. >> >> >> Does anybody have an idea what I do wrong? It really sucks to be stuck at >> this point, I really would appreciate any help here. >> >> >> Thanks in advance & greetings, >> Axel. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/puppet-dev/-/0hSsomXXmRoJ. >> To post to this group, send email to [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/puppet-dev?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/UOEzKGD6S30J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
