Debian Patches
Status for puppet-module-puppetlabs-rabbitmq/8.5.0-11
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| do-not-download-rabbitmqadmin-in-debian.patch | Do not download rabbitmqadmin in Debian | Thomas Goirand <zigo@debian.org> | no | 2019-04-08 | ||
| correctly-report-rabbitmq-version.patch | Correctly report rabbitmq version The output of "rabbitmqctl -q status" has changed between Buster and Bullseye, confusing this puppet module. This fixes the problem. As the version is now correctly detected, this puppet module can now correctly use the --no-table-headers parameters for querying Rabbit. |
Thomas Goirand <zigo@debian.org> | yes | 2021-03-10 | ||
| add-minus-q-when-calling-rabbitmq-plugin-list.patch | Add -q when calling rabbitmq-plugins list The -q is needed in the Bullseye version to avoid the hearder. | Thomas Goirand <zigo@debian.org> | no | 2021-01-21 | ||
| increase-rabbitmq-timeout.patch | Increase rabbitmq cli timeout The new version of rabbitmq is taking much longer to reply, which often goes below the timeout of 10 seconds, resulting in the rabbitmq puppet providers to just fail. Increasing to 20 seconds just fixes it for me. =================================================================== |
Thomas Goirand <zigo@debian.org> | no | 2021-01-21 | ||
| trixie-support.patch | Trixie support | Thomas Goirand <zigo@debian.org> | no | 2025-05-27 | ||
| fix-list_users-provider.patch | Fix list_users provider =================================================================== |
Thomas Goirand <zigo@debian.org> | yes | 2025-05-29 | ||
| setup-all-nodes-as-disk-nodes.patch | Setup all nodes as disk nodes In most production setups, it is advised to set all nodes as disk nodes bacause of: * Simplicity – all nodes behave the same; no special recovery procedures. * Resilience – if one disk node fails, you don’t risk being left with only RAM nodes (which could cause data loss if all RAM nodes restart). * Operational flexibility – you can remove or add nodes without worrying about “last disk node” constraints. * Modern RabbitMQ performance – RAM nodes used to help in early versions (pre-3.x) when Mnesia disk I/O was slow, but with current disk and SSD speeds, the performance difference is often negligible. |
Thomas Goirand <zigo@debian.org> | no | 2025-08-11 |