Scale out of rabbitmq is broken
Bug #1785569 reported by
Michal Nasiadka
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
When adding additional hosts - rabbitmq always keeps restarting with following messages in the logs:
+ exec /usr/sbin/
=INFO REPORT==== 6-Aug-2018:
Clusterer stopping node now.
This is because kolla-ansible puts static "version 1" in rabbit-
Ideally when deploying a new node we should check current clusterer config version and bump it up to allow scale-out.
| affects: | kolla → kolla-ansible |
Revision history for this message
| Michal Nasiadka (mnasiadka) wrote | #1 |
| Changed in kolla-ansible: | |
| status: | New → Invalid |
To post a comment you must log in.
From: https:/
version: non negative integer
All configs are versioned and this is used to decide which of any two configs is the youngest. A config which has a smaller version number is older. Configs will be ignored unless they are younger than the current config. Note that in lieu of any config being provided by the user, the default config is used which has a version of 0. Thus user supplied configs should use a version of 1 or greater.