Remove -q from rabbitmq-plugins list

[DeWaRs]

"-q" doesn't seems to be a valid argument:

root@manu-ubuntu2:/var/log/rabbitmq# rabbitmq-plugins
Error: could not recognise command
Usage:
rabbitmq-plugins [-n <node>] <command> [<command options>]

Commands:
    list [-v] [-m] [-E] [-e] [<pattern>]
    enable [--offline] [--online] <plugin> ...
    disable [--offline] [--online] <plugin> ...
    set [--offline] [--online] <plugin> ...

This -q breaks the recipe mgmt_console and I guess any recipe the use this providers.

Proposed Changes

Please describe the big picture of your changes here to communicate to the
RabbitMQ team why we should accept this pull request. If it fixes a bug or
resolves a feature request, be sure to link to that issue.

A pull request that doesn't explain why the change was made has a much
lower chance of being accepted.

If English isn't your first language, don't worry about it and try to
communicate the problem you are trying to solve to the best of your abilities.
As long as we can understand the intent, it's all good.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes issue #NNNN)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (correction or otherwise)
• Cosmetics (whitespace, appearance)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in related repositories

Further Comments

If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

[michaelklishin]

My best guess is that you tried to provision a version other than 3.7.x. All earlier release series have been out of support since at least May 2018.

[DeWaRs]

@michaelklishin this is correct. Why the default version deploy by this cookbook is 3.6.16 then ? Any chances to change that?

[michaelklishin]

3.7.x will be the only supported version in 6.0 but #442 and #497 have to be addressed first. Our team has no ETA on when that might happen but we understand that having at least some fundamental bits in place for contributors to help is a very important step towards 6.0.

Another problem is that 3.7.x requires OTP 20.3+ and the Erlang cookbook this one depends on has been lagging behind. The package availability problem has long been solved by our team but it is yet to make it to the Erlang cookbook.