Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Henrik Lindberg Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Nicholas Fagerlund i think the fix makes it work the way you'd expect. If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. Previously the autoloader would load types and providers from the default environment (production) during one phase of the compilation. The fix is to ensure we autoload types and providers from the same environment that is specified. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Fagerlund commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Eric Thompson Okay, so it sounds like the problem was just with providers, and just with resources that specified the provider attribute, right? Could you please update the description to describe that? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Fagerlund assigned an issue to Eric Thompson Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Nicholas Fagerlund Assignee: NicholasFagerlund EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Thomas Hallgren Assignee: ThomasHallgren Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Merged to stable at 966f81b Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Kurt Wall commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Verified in master at SHA=af02828c7b16aa9c3b9823ba21b9cd60425b9745. Using eric0's reproducer, here's an agent run: # puppet agent --test --environment production Info: Retrieving pluginfacts Info: Retrieving plugin Notice: /File[/var/lib/puppet/lib/puppet]/ensure: removed Info: Caching catalog for g9nzizk8lqji3m6.delivery.puppetlabs.net Info: Applying configuration version '1422565122' Notice: current environment is production Notice: /Stage[main]/Main/Node[default]/Notify[environment]/message: defined 'message' as 'current environment is production' Notice: Applied catalog in 0.02 seconds
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title
Kurt Wall commented on PUP-1515
Re: Invalid parameter provider for custom types/providers
I get the same result if I run against the fail environment before the production environment.
# puppet agent --test --environment fail
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[/var/lib/puppet/lib/puppet]/ensure: created
Notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created
Notice: /File[/var/lib/puppet/lib/puppet/provider/vcsrepo]/ensure: created
Notice: /File[/var/lib/puppet/lib/puppet/provider/vcsrepo.rb]/ensure: defined content as '{md5}dbd72590771291f1db23a41ac048ed9d'
Notice: /File[/var/lib/puppet/lib/puppet/provider/vcsrepo/bzr.rb]/ensure: defined content as '{md5}9304caa8c45685d741248fb167c47842'
Notice: /File[/var/lib/puppet/lib/puppet/provider/vcsrepo/cvs.rb]/ensure: defined content as '{md5}0fed7f40f3de82c6490ac241cea46b3a'
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Henrik Lindberg Fix Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Reopened as a backport is wanted to 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Brook Shelley commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Updated note from Sales, is that the customer is somewhat unwilling to move to 3.7.x Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Eric Thompson QA Contact: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Steve Barlow Sprint: Language2015-01-21 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Josh Cooper commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Merged to master in fcc85689 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Gabriele Paggi commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Charlie Sharpsteen Thanks! I didn't have the environment set in the master section indeed. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Gabriele Paggi commented on PUP-1515 Re: Invalid parameter provider for custom types/providers So, to summarize: when the Puppet master loads a Type, it searches the environment that the agent requested. When it loads providers for that type, it searches the default environment instead of the one the agent requested. Charlie Sharpsteen, what is the name of the default environment? Is it production? I'm seeing the same issue with only one environment named prd. The workaround I'm using is to define a production environment pointing to the same directories as the prd one: # Always create production pointing to the first defined environment # to circumvent PUP-1515 (pluginsync, custom provider/type) [production] manifest = /etc/puppet/environments/prd/manifests/ modulepath = /etc/puppet/environments/prd/. [prd] manifest = /etc/puppet/environments/prd/manifests/ modulepath = /etc/puppet/environments/prd/..
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Gabriele Paggi The default environment for the master is usually, almost nearly always production. Specifically, the default is whatever the environment setting has been set to in the master section of puppet.conf. Since most people don't set that, production is used. You can check what the value of the default environment is by running the following on a Puppet master: puppet config print --section master environment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Joshua Partlow commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Commented on the PR; Charlie's patch looks like the correct behavior to me. A test run of acceptance on rhel7 passed as well. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Dirk Heinrichs commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Any chance to get this fixed in 3.7.x instead of 4.0.0? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Sorenson commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Dirk Heinrichs there is probably not going to be another 3.x release until just before 4.0 comes out so it wouldn't change things much. As an aside, did you try the patch? Did it work for you? Kylo Ginsberg can you estimate how much work it would take to get the patch up to snuff? I'm not even sure how you'd test this in a before-and-after sense, but there are a ton of people interested in this bug and I'd hate to see it miss the train. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Kylo Ginsberg commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Eric Sorenson I just threw an estimate down for velocity purposes. We reviewed Charlie Sharpsteen's PR at last PR triage and all (me/Henrik/JoshC) agreed that it makes sense on paper. However, given that it's about environments - a central and sometimes nuanced area of the code - we did want Joshua Partlow to take a look at the PR for any reservations, etc. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Richard Raseley commented on PUP-1515 Re: Invalid parameter provider for custom types/providers We are also hitting this issue when using puppet-3.7.3-1.el7 on CentOS Linux release 7.0.1406 (3.10.0-123.el7.x86_64), which is blocking us on a couple items. I will try to find the time tomorrow to check and see if the patch (https://github.com/puppetlabs/puppet/pull/2963) mentioned by Charlie Sharpsteen resolves the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen AndyParker Add Comment 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Charlie Sharpsteen Component/s: Server Add Comment 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen commented on an issue Re: Invalid parameter provider for custom types/providers So, what is happening here is that the Autoloader isn't switching environments correctly. When the Vcsrepo type is loaded, a call of this form is used: typeloader.load(name, Puppet.lookup(:current_environment)) Where the typeloader is an Autoloader instance. In this case, we explicitly pass the current environment that the master is compiling for. Once the type is loaded, we then load all known providers for that type: klass.providerloader.loadall Where providerloader is another Autoloader instance. Note that no environment is passed to this call. Because no environment is passed, there are two places where nil gets used instead. This causes the Autoloader to search Puppet[:environment] instead of the current_environment. So, to summarize: when the Puppet master loads a Type, it searches the environment that the agent requested. When it loads providers for that type, it searches the default environment instead of the one the agent requested. Andy Parker: This is a different issue from PUP-731 and one that we could fix. Handing back to you to decide if this should be scheduled for a release. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Andy Parker updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Andy Parker Fix Version/s: 4.0.0 Add Comment 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Andy Parker commented on an issue Re: Invalid parameter provider for custom types/providers I've encountered this code before. Unfortunately we don't have time before 3.7 to get a fix in for this. I'm going to target it at 4.0.0 instead, since fixing it might also cause some API breaks. 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Sorenson commented on an issue Re: Invalid parameter provider for custom types/providers Wow, that's great. Sounds like a very targeted fix that could help a lot of people. Would it be possible to get a branch or DO NOT MERGE PR up with a quick spike? That way people affected by it could try out the branch to see if it works in their environments. 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen commented on an issue Re: Invalid parameter provider for custom types/providers Eric Sorenson: I've put the patch I developed while investigating this issue up as PR 2963. No tests, no guarantees. But, if someone tries it out and it works, please do let us know! 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Andy Parker assigned an issue to Charlie Sharpsteen Charlie Sharpsteen is going to take a look into this and see if this is definitively related to PUP-731 or not. If it is, then there isn't really anything we can do about it with the current master setups. If it isn't, then his investigation should uncover a bit clearer the source of the problem. Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Andy Parker Assignee: EricSorenson CharlieSharpsteen Add Comment 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title cristi falcas commented on an issue Re: Invalid parameter provider for custom types/providers Any news about the status of this? Currently we can't use multiple environments because of this. Well, actually we use a development environment for our puppet masters where we keep all our modules in order to mitigate this. 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Tom De Vylder commented on an issue Re: Invalid parameter provider for custom types/providers I'm running into the same behavior with: 3.6.2-1puppetlabs1 3.6.1-1puppetlabs1 3.5.1-1puppetlabs1 (from apt.puppetlabs.com) ... using puppet apply on Puppetlabs' current Debian 7 Vagrant box (http://puppet-vagrant-boxes.puppetlabs.com/debian-73-x64-virtualbox-puppet.box). 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Miguel Di Ciurcio Filho updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Miguel Di Ciurcio Filho Affects Version/s: 3.6.2 Add Comment 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.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Martin Mrner commented on an issue Re: Invalid parameter provider for custom types/providers Please fix this bug as any currently advocated development method with environments and usage of r10k builds works against this. Especially when using official modules like puppetlabs/mysql: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider on Mysql_database[foo] at /etc/puppet/environments/dev_mysql/modules/mysql/manifests/db.pp:27 on node... /etc/puppet/puppet.conf [main] environment = production confdir = /etc/puppet logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter pluginsync = true [master] environment = production environmentpath = $confdir/environments autosign = false ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY storeconfigs = true storeconfigs_backend = puppetdb reports = puppetdb [agent] environment = production server = *** report = true 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title vinod kumar commented on an issue Re: Invalid parameter provider for custom types/providers I also observed the similar behavior with custom environment path. Following is the alternate to work with: Install puppet module without any environment i.e. puppet module install puppetlabs-vcsrepo This will install the vcsrepo module under $puppet-conf-dir/modules directory. Now, you can access puppet agent with the custom environment like puppet agent --test --environment fail Also enable 'pluginsync = true' in puppet.conf file Hope this will work for every one as it is working for me. 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 ...
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Andreas Ntaflos commented on an issue Re: Invalid parameter provider for custom types/providers Me, too. Our Puppet master currently runs in the 'production' environment while a growing number of nodes run in a different environment (called 'production_redux', as we are overhauling the Puppet infrastructure on that site). Using the puppetlabs-mysql module in the 'production_redux' environment (but not in 'production') we get the invalid parameter provider exception trying to manage MySQL users and databases. Do I understand correctly that switching the Puppet master's own environment to (in our case) 'production_redux' would work around this problem? FWIW, running puppet plugin download --environment production_redux on the Puppet master results in this: # puppet plugin download --environment production_redux Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet://puppet01.example.com/plugins: undefined method `intern' for nil:NilClass Wrapped exception: undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources using 'eval_generate': undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet://puppet01.example.com/pluginfacts: undefined method `intern' for nil:NilClass Wrapped exception: undefined method `intern' for nil:NilClass No plugins downloaded. I have no idea what to make of this. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Hinds commented on an issue Re: Invalid parameter provider for custom types/providers In case people are interested, it's possible to work around this bug for a small number of agents by running a plugin sync on the puppet master before applying the configuration on the puppet agent; of course, this doesn't scale nor does it allow you to setup agents to poll the puppet master unless they're in the default production environment: Run puppet plugin download --environment ENVIRONMENT-NAME-HERE service puppetmaster restart on the puppet master to make the plugins available in the correct place Apply the puppet configuration on the puppet agent (puppet agent -t) Run puppet plugin download service puppetmaster restart on the puppet master to restore the original plugins 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 ...
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Matt Wise commented on an issue Re: Invalid parameter provider for custom types/providers We're seeing this as well on our Puppet 3.4.1 servers. We had to copy the library into our 'master' branch of code in order for it to work anywhere. This is a huge bug because it makes doing development work on other branches difficult. 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Net Kgk commented on an issue Re: Invalid parameter provider for custom types/providers I've got this issue, with next settings: ... [master] ... environment = production ... manifest = $confdir/environments/$environment/manifests/site.pp modulepath = $confdir/environments/$environment/modules ... Then, when I've updated different environment (let's say test) with new module (puppet-labs/mysql), I've got this exception on master while running puppet agent with --environment='test' on different host, because puppet-labs/mysql was absent in production 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)
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Alejandro Figueroa commented on an issue Re: Invalid parameter provider for custom types/providers I can confirm Net Kgk's diagnosis. The module was different on my servers (puppetlabs/vcsrepo) but the results were the same. 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/groups/opt_out.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Sorenson commented on an issue Re: Invalid parameter provider for custom types/providers Net Kgk Alejandro Figueroa i am having trouble reproducing this issue. is it true in your case that, as Andy Shinn said on the redmine bug my default environment for the puppetmaster doesn’t have some new types I am testing in another environment and when testing that environment it is failing. ?? 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Joshua Chaitin-Pollak commented on an issue Re: Invalid parameter provider for custom types/providers You didn't tag me, but I can confirm our postmaster has a default configuration of the puppet environment, but is configured to serve one of two different puppet libraries based on parameters of the connected client. In other words, I believe out puppet master executes with a different set of puppet modules than it serves to clients, which I think is what people say causes this situation. 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Net Kgk updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Net Kgk Priority: Normal Critical Add Comment 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/groups/opt_out.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Net Kgk commented on an issue Re: Invalid parameter provider for custom types/providers This issue makes it impossible to use any native type with environments (which is officially recommended approach), so raising priority. 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/groups/opt_out.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title redmine.exporter created an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Issue Type: Bug Assignee: Eric Sorenson Created: 24/Jan/14 2:29 PM Labels: redmine Priority: Normal Reporter: redmine.exporter 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 able to reproduce and fix the issue. Add Comment
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title
Joshua Chaitin-Pollak commented on an issue
Re: Invalid parameter provider for custom types/providers
I am experiencing a similar issue with puppet 3.4.2. I've posted here as well (https://github.com/puppetlabs/puppetlabs-vcsrepo/issues/118), I apologize in advance for crossposting, I'm not sure if this is a Puppet issue or a vcsrepo one.
I have the following configuration:
vcsrepo { $directory : ensure = latest, provider = git, source = g...@github.com:example/project.git, revision = $revision, user = $user, require = Class['::nginx'], }
And when I run puppet agent on my node, I get this error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /var/lib/puppet/modules/project/manifests/init.pp:21 on node mynode.example.com This error is repeated in the puppetmaster's log as well.
I restarted the puppet master, but that didn't solve the problem. I did verify that the git.rb file is in the puppet repository.
Both the master and slave are running Puppet 3.4.2
Any help would be appreciated.
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 ...
