Issue #17814 has been updated by Drew Blessing. Status changed from Needs More Information to Closed
Problem solved. It was because the puppetmaster hadn't run and picked up the new plugins. I find it a little odd that the puppetmaster even cares what types/providers are available since it's the client that cares and did have the plugins. Anyway, this appears to be an environment issue and not a bug. ---------------------------------------- Bug #17814: Invalid parameter provider for custom types/providers https://projects.puppetlabs.com/issues/17814#change-77518 Author: Drew Blessing Status: Closed 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.
