diff options
author | Tomas Sedovic <tomas@sedovic.cz> | 2017-09-13 17:44:45 +0200 |
---|---|---|
committer | Tomas Sedovic <tomas@sedovic.cz> | 2017-09-13 17:44:45 +0200 |
commit | 8a204aaec709135ebfa716459f2ba3bcf1db4f04 (patch) | |
tree | 4897fe7905a11fed34e471236f2a202f7f81effe /playbooks/provisioning/openstack/galaxy-requirements.yaml | |
parent | c478cfcd54bc89918bea21b9e47fcc9421bec568 (diff) | |
download | openshift-8a204aaec709135ebfa716459f2ba3bcf1db4f04.tar.gz openshift-8a204aaec709135ebfa716459f2ba3bcf1db4f04.tar.bz2 openshift-8a204aaec709135ebfa716459f2ba3bcf1db4f04.tar.xz openshift-8a204aaec709135ebfa716459f2ba3bcf1db4f04.zip |
Clear the previous inventory during provisioning
If there was a left-over inventory from a previous run that had nodes
which were subsequently removed, these would still show up in the
Ansible's in-memory inventory and Ansible would fail trying to connect
to them.
This is because Ansible automatically loads the `inventory/hosts` file
if it exists and even if we overwrite it later, every node and group
still remains in the memory.
By removing the inventory file and and calling the `refresh_inventory`
meta task, we make sure that any left-over values are removed.
Diffstat (limited to 'playbooks/provisioning/openstack/galaxy-requirements.yaml')
0 files changed, 0 insertions, 0 deletions