Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: Invalid parameter provider for custom types/providers Eric's re-production steps for 3.5.1 still work on 3.6.2. Here is a backtrace from the master: [root@poss-head-centos ~]# puppet master --no-daemonize --trace --verbose Notice: Starting Puppet master version 3.6.2 Info: Inserting default '~ ^/catalog/([^/]+)$' (auth true) ACL Info: Inserting default '~ ^/node/([^/]+)$' (auth true) ACL Info: Inserting default '/file' (auth ) ACL Info: Inserting default '/certificate_revocation_list/ca' (auth true) ACL Info: Inserting default '~ ^/report/([^/]+)$' (auth true) ACL Info: Inserting default '/certificate/ca' (auth any) ACL Info: Inserting default '/certificate/' (auth any) ACL Info: Inserting default '/certificate_request' (auth any) ACL Info: Inserting default '/status' (auth true) ACL Info: Inserting default '/v2.0/environments' (auth true) ACL Info: Caching node for poss-head-centos.puppetdebug.vlan Info: Caching node for poss-head-centos.puppetdebug.vlan Error: Invalid parameter provider on Vcsrepo[dotfiles] at /etc/puppet/environments/fail/manifests/site.pp:10 on node poss-head-centos.puppetdebug.vlan /puppetlabs/puppet/lib/puppet/resource.rb:442:in `validate_parameter' /puppetlabs/puppet/lib/puppet/parser/resource.rb:264:in `block in validate' /puppetlabs/puppet/lib/puppet/parser/resource.rb:263:in `each' /puppetlabs/puppet/lib/puppet/parser/resource.rb:263:in `validate' /puppetlabs/puppet/lib/puppet/parser/resource.rb:107:in `finish' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:442:in `block in finish' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:430:in `each' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:430:in `finish' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:128:in `block (2 levels) in compile' /puppetlabs/puppet/lib/puppet/util/profiler/none.rb:6:in `profile' /puppetlabs/puppet/lib/puppet/util/profiler.rb:43:in `profile' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:128:in `block in compile' /puppetlabs/puppet/lib/puppet/context.rb:64:in `override' /puppetlabs/puppet/lib/puppet.rb:234:in `override' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:106:in `compile' /puppetlabs/puppet/lib/puppet/parser/compiler.rb:23:in `compile' /puppetlabs/puppet/lib/puppet/indirector/catalog/compiler.rb:95:in `block (2 levels) in compile' /puppetlabs/puppet/lib/puppet/util/profiler/none.rb:6:in `profile' /puppetlabs/puppet/lib/puppet/util/profiler.rb:43:in `profile' /puppetlabs/puppet/lib/puppet/indirector/catalog/compiler.rb:93:in `block in compile' /puppetlabs/puppet/lib/puppet/util.rb:161:in `block in benchmark' /opt/rh/ruby193/root/usr/share/ruby/benchmark.rb:295:in `realtime' /puppetlabs/puppet/lib/puppet/util.rb:160:in `benchmark' /puppetlabs/puppet/lib/puppet/indirector/catalog/compiler.rb:92:in `compile' /puppetlabs/puppet/lib/puppet/indirector/catalog/compiler.rb:52:in `find' /puppetlabs/puppet/lib/puppet/indirector/indirection.rb:201:in `find' /puppetlabs/puppet/lib/puppet/network/http/api/v1.rb:105:in `do_find' /puppetlabs/puppet/lib/puppet/network/http/api/v1.rb:50:in `block in call' /puppetlabs/puppet/lib/puppet/context.rb:64:in `override' /puppetlabs/puppet/lib/puppet.rb:234:in `override' /puppetlabs/puppet/lib/puppet/network/http/api/v1.rb:49:in `call' /puppetlabs/puppet/lib/puppet/network/http/route.rb:82:in `block in process' /puppetlabs/puppet/lib/puppet/network/http/route.rb:81:in `each' /puppetlabs/puppet/lib/puppet/network/http/route.rb:81:in `process' /puppetlabs/puppet/lib/puppet/network/http/handler.rb:63:in `block in process' /puppetlabs/puppet/lib/puppet/util/profiler/none.rb:6:in `profile' /puppetlabs/puppet/lib/puppet/util/profiler.rb:43:in `profile' /puppetlabs/puppet/lib/puppet/network/http/handler.rb:61:in `process' /puppetlabs/puppet/lib/puppet/network/http/webrick/rest.rb:37:in `block in service' <internal:prelude>:10:in `synchronize' /puppetlabs/puppet/lib/puppet/network/http/webrick/rest.rb:36:in `service' /opt/rh/ruby193/root/usr/share/ruby/webrick/httpserver.rb:138:in `service' /opt/rh/ruby193/root/usr/share/ruby/webrick/httpserver.rb:94:in `run' /puppetlabs/puppet/lib/puppet/network/http/webrick.rb:36:in `block (2 levels) in listen' /opt/rh/ruby193/root/usr/share/ruby/webrick/server.rb:191:in `call' /opt/rh/ruby193/root/usr/share/ruby/webrick/server.rb:191:in `block in start_thread' So, compilation is dying in the very last stage when the master is validating the catalog contents before shipping it to the agent. Also worth noting is that the master environment will be "production" unless set to something else: [30] pry(#<Puppet::Parser::Resource>)> Puppet[:environment] => "production" My current theory is: the master can load types from the environment requested by the agent, but it can only load providers from it's own environment. Hence, the Vcsrepo Type is acting like an old primordial Type from the time before providers existed (Yumrepo used to be one of these until it was refactored in 3.5.0). If no providers are loaded, Type.providify never gets called and this method defines the provider parameter that the validator is failing to see. If the master is launched with the same environment that the agent will use, the error disappears: puppet master --no-daemonize --trace --verbose --environment fail I'll dig some more tomorrow to see if my theory is correct. If it is, then this is a bit different than PUP-731 and I'll try to determine why the master is not loading providers from the agent environment. Add Comment   Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.