Bug #8767
open
Foreman removes wrong DNS entry for openstack VM
Description
I have a environment where Foreman and openstack hosts are in the same network space, 10.10.10.0. The float address space for the openstack VM are 10.10.20.0 and their private address are 192.168.1.0.
When foreman starts a VM, it gets the float address and assigns the DNS entry for it, say 10.10.20.1. After the VM is used and removed, foreman removes a entry for the private address, 192.168.1.2.
This causes a problem when bringing up the next VM as it can get the same float address and a conflict in the DNS record will happen.
I am using version 1.7.0 of foreman.
Updated by Stephen Benjamin over 9 years ago
Foreman gets IP addresses from Facter (and facter can only ever know about the tenant IP). Foreman updates the host with that info.
I'm assuming that's what's happening here. For OpenStack instances, we should probably not do that by default? Anyway, you can try going into settings, and setting this one to true: 'ignore_puppet_facts_for_provisioning'
That should hopefully fix the problem for you for now.
Updated by Brian Lee over 9 years ago
I was on that path right as you commented. I changed that setting and now it seems to remove the correct DNS entry.
Thanks for the input!
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3864: Change ignore_puppet_facts_for_provisioning default to true added