eaa81c11fc
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: Id35480d5d0cf6316e31fe1b287421bfb56e20685 Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
11 lines
384 B
YAML
11 lines
384 B
YAML
---
|
|
|
|
upgrade:
|
|
- |
|
|
Default value of ``haproxy_ssl_letsencrypt_certbot_bind_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.
|