On Mon, Aug 22, 2011 at 7:35 AM, nothings_absolute <soren.mor...@gmail.com> wrote: > > Well... If there aren't any ideas on the cause can anyone tell me > if I am using ParsedFile correctly? Or if there is a resource for > documentation on this class? I am just beginning to use ruby so trying > to figure out what is provided by the class by looking at the source > is going to be difficult.
You can look at other types and provider based on ParsedFile. I don't believe there's any official documentation. > On Aug 18, 2:31 pm, nothings_absolute <soren.mor...@gmail.com> wrote: >> I have been messing with this for a while and have had no luck so >> hoping someone here can help. >> >> I created a customer type called autofs and a provider that uses >> ParsedFile to parse the auto_direct file according to what I found >> here:http://www.kartar.net/2010/02/puppet-parsedfile-types-and-providers/ >> >> The type is located at .../devl/common/lib/puppet/type/autofs.rb >> The provider is located at .../devl/common/lib/puppet/provider/autofs/ >> autofs.rb >> >> I get the following when running puppetd: >> ... >> notice: /File[/var/opt/lib/puppet]/ensure: created >> notice: /File[/var/opt/lib/puppet/provider]/ensure: created >> notice: /File[/var/opt/lib/puppet/provider/autofs]/ensure: created >> notice: /File[/var/opt/lib/puppet/provider/autofs/autofs.rb]/ensure: >> defined content as '{md5}8469013512e708aaf85740caecae74b8' >> notice: /File[/var/opt/lib/puppet/type]/ensure: created >> notice: /File[/var/opt/lib/puppet/type/autofs.rb]/ensure: defined >> content as '{md5}66817f006dd23e31556e88a3aa837fd2' >> info: Loading downloaded plugin /var/opt/lib/puppet/type/autofs.rb >> info: Loading downloaded plugin /var/opt/lib/puppet/provider/autofs/ >> autofs.rb >> debug: Reloading parsed autofs provider >> ... >> err: Could not retrieve catalog from remote server: Error 400 on >> SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: >> Invalid resource type autofs at .../devl/base/manifests/autodf.pp:8 on >> node testserver.test.com The issue here appears to be a problem with puppet master finding your custom type. I don't know if /devl/ is part of your puppet master module path. Check your config and you can also try: RUBYLIB=.../devl/common/lib/ puppet master --no-daemonize -v Also if you just developing it, puppet apply with the appropriate module path might be easier to troubleshoot than the full agent/master mode. Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
