Issue #17814 has been updated by Ewoud Kohl van Wijngaarden. Status changed from Closed to Re-opened
This sounds a lot like #13858, but for providers instead of types. I just ran into this as well (tried both puppet 2.7.20 and 3.0.2). One way to reproduce is as follows: * Set up a puppet master on server A * Make server B a puppet client of server A * Set up another puppet master on server B * Make server C a puppet client of server B * Add a puppet module with custom providers (I used puppet-mysql from puppetlabs) to the modules B serves to C, but is not available in the modules A serves to B. Now when we try to use the module with providers on C we run in the 'invalid parameter provider' error. Installing the module on server A, then syncing server B (so the plugins are synced) will solve the problem for server C. ---------------------------------------- Bug #17814: Invalid parameter provider for custom types/providers https://projects.puppetlabs.com/issues/17814#change-81395 Author: Drew Blessing Status: Re-opened Priority: Urgent Assignee: Category: provider Target version: Affected Puppet version: 3.0.1 Keywords: Branch: 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. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. 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-bugs?hl=en.
