Project

General

Profile

Actions

Bug #8767

open

Foreman removes wrong DNS entry for openstack VM

Added by Brian Lee about 10 years ago. Updated about 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #3864: Change ignore_puppet_facts_for_provisioning default to trueRejected12/12/2013Actions
Actions

Also available in: Atom PDF