-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invalid parameter provider #49
Comments
Can you retest this with the code in git? I've made a bunch of changes in the last month and I think this should work fine for you now. |
I'll test as soon as I get back from vacation.. (in ~2 weeks). |
I was having this same problem when I realized that I was using the rpm from the epel repository and not the rpm from the rabbitmq repository (epel now has version 3.1.5-1). The epel version does not have the rabbmq-plugins command. Once I installed the rpm from the rabbitmq repository, things worked as I expected. |
I am having the same issue on Ubuntu. |
Guys, I had the same issue but this was because of the old RabbitMQ (2.7) in Ubuntu 12.04. I simply forgot to upgrade to latest 3.1 and then it all worked as expected. |
Guessing this should be not an issue with any current versions that would get installed? I'm going to close, but re-open if this is still an issue. |
I'm getting:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider..
From this:
rabbitmq_plugin {'rabbitmq_management':
ensure => present,
provider => 'rabbitmqplugins',
}
If I remove the provider - it uses the default (which does nothing but fail :)
I tried (just to test) - to move the rabbitmqplugins.rb to default.rb - but then it just says:
err: Could not find a suitable provider for rabbitmq_plugin
Using puppet-2.7.21 - and just pulled latest puppetlabs-rabbitmq..
Any ideas as to what's up?
The text was updated successfully, but these errors were encountered: