-
-
Notifications
You must be signed in to change notification settings - Fork 500
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
rabbitmq_plugin not working properly with RabbitMQ 3.10.x #909
Labels
bug
Something isn't working
Comments
kvisle
added a commit
to kvisle/puppet-rabbitmq
that referenced
this issue
Aug 12, 2022
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when enumerating enabled plugins. Starting with rabbitmq 3.10, this command will output a informational message: 'Listing plugins with pattern ".*" ...' which can be hidden with the -s or -q parameter. However, this approach will break rabbitmq_plugin on older versions of RabbitMQ. This patch implements a workaround that simply ignores the outputted line if it exists. Fixes: voxpupuli#909
kvisle
added a commit
to kvisle/puppet-rabbitmq
that referenced
this issue
Aug 12, 2022
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when enumerating enabled plugins. Starting with rabbitmq 3.10, this command will output a informational message: 'Listing plugins with pattern ".*" ...' which can be hidden with the -s or -q parameter. However, this approach will break rabbitmq_plugin on older versions of RabbitMQ. This patch implements a workaround that simply ignores the outputted line if it exists. Fixes: voxpupuli#909
kvisle
added a commit
to kvisle/puppet-rabbitmq
that referenced
this issue
Aug 12, 2022
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when enumerating enabled plugins. Starting with rabbitmq 3.10, this command will output a informational message: 'Listing plugins with pattern ".*" ...' which can be hidden with the -s or -q parameter. However, this approach will break rabbitmq_plugin on older versions of RabbitMQ. This patch implements a workaround that simply ignores the outputted line if it exists. Fixes: voxpupuli#909
wyardley
added a commit
to wyardley/puppet-rabbitmq
that referenced
this issue
Aug 12, 2022
Resolve an issue with extra output from `rabbitmq_plugin` in versions >= 3.10.x Fixes voxpupuli#909
kvisle
added a commit
to kvisle/puppet-rabbitmq
that referenced
this issue
Aug 13, 2022
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when enumerating enabled plugins. Starting with rabbitmq 3.10, this command will output a informational message: 'Listing plugins with pattern ".*" ...' which can be hidden with the -s or -q parameter. However, this approach will break rabbitmq_plugin on older versions of RabbitMQ. This patch implements a workaround that simply ignores the outputted line if it exists. Fixes: voxpupuli#909
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Abovementioned command returns the following:
What behaviour did you expect instead
A list of plugin resources and their ensured status.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: