Use management address when available

In case of defining different IP address for SSH and Management
network in metal scenario, as described in [1], you get SSH address
defined as `ansible_host`, which results in HAProxy configuring
backends on SSH address rather then management one, where
service is actually listening.
We use `ansible_host` as a fallback for non-OSA usage of the role.
[1] https://docs.openstack.org/openstack-ansible/latest/reference/inventory/configure-inventory.html#having-ssh-network-different-from-openstack-management-network
Change-Id: I85a164b181b41025f8f872dbdf5426bf58f6f36e
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
This commit is contained in:
Dmitriy Rabotyagov
2025年09月03日 17:43:53 +02:00
parent 46b7f5114a
commit 4d098fed10

View File

@@ -28,7 +28,7 @@ rabbitmq_erlang_package_version: "26.2.*-1"
rabbitmq_host_group:"rabbitmq_all"
# The local address used for the rabbitmq cluster node
rabbitmq_node_address:"{{ ansible_host }}"
rabbitmq_node_address:"{{ management_address | default(ansible_host) }}"
rabbit_system_user_name:rabbitmq
rabbit_system_group_name:rabbitmq

View File

@@ -0,0 +1,9 @@
---
upgrade:
- |
Default value of ``rabbitmq_node_address`` has changed from
``ansible_host``, which could vary based on the deployment scenario,
to ``management_address``, which will be set to the IP of the
management network.
The fallback to ``ansible_host`` is present to avoid failures when
``management_address`` is not defined.
Reference in New Issue
openstack/openstack-ansible-rabbitmq_server
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.