7434bed989
This addresses an issue with delegation to containers noticed as a result of https://github.com/ansible/ansible/issues/72776 which causes the container host to be accessed by its hostname. Where a separate deploy host is used, up to now this has not had its hosts file modified. This patch applies the same /etc/hosts entries to the deploy host which are used elsewhere. Change-Id: I82b48ba5cfe6e533426e7098c455b729084b2d51
14 lines
651 B
YAML
14 lines
651 B
YAML
---
|
|
features:
|
|
- |
|
|
In deployments where a separate host is used to manage the OpenStack
|
|
Ansible configuration, the '/etc/hosts' file on that host will now include
|
|
a section adding hostname to IP resolution for all hosts in the inventory.
|
|
This can be enabled/disabled via 'openstack_host_manage_deploy_hosts_file'.
|
|
issues:
|
|
- |
|
|
Where a single OSA deploy host is used to manage multiple deployments, some
|
|
delegated Ansible tasks are performed using hostnames rather than IP
|
|
addresses due to Ansible issue 72776. Hostnames such as 'infra1' will be
|
|
ambiguous, so use of separate hosts for each deployment is recommended.
|