46862920df
This fixes an issue, when a host group was passed to mq_setup role, and delegate logic uses group name instead of host inside of the group for delegating tasks. While this patch might break already in-place workarounds, it's quite important to fix the issue properly, as workarounds are not trivial and requires quite some understanding of the process. Closes-Bug: #2111406 Change-Id: Ic5747e29050cced51a71a4b4e71352f231758ed8
15 lines
617 B
YAML
15 lines
617 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
When using standalone RabbitMQ cluster for Trove deployment, make sure to
|
|
use ``trove_guest_rpc_host_group`` as a pointer to host group, rather then
|
|
a pointer to a specific host.
|
|
You can use variable ``trove_guest_oslomsg_rpc_setup_host`` to define a
|
|
specific host which should be responsible for provisionment of RabbitMQ
|
|
vhost and users instead.
|
|
fixes:
|
|
- |
|
|
Variable ``trove_guest_rpc_host_group`` is now used as intended and
|
|
represents a host group. It is no longer directly used as
|
|
"delegated host" when configuring a standalone RabbitMQ cluster for Trove.
|