Bug #16105: DNS entries are not created if discovery hostname is the same as the provisioned (managed) host name - Discovery - Foreman

Actions

Copy link

Bug #16105

closed

DNS entries are not created if discovery hostname is the same as the provisioned (managed) host name

Added by Imri Zvik over 7 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Low

Assignee:

Imri Zvik

Category:

Discovery plugin

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman_discovery/pull/297

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

For example, if the hostname of the discovered host is 'foo.example.com' (coming from custom fact, for example), and that is the hostname you provision the host, and use the IP already allocated to the machine in the discovery process (by DHCP), Orchestration::DNS.pending_dns_record_changes? will return false, and thus will not create DNS records for the host.
I see few possibilities for remediation:

Make pending_dns_record_changes? actually check for the existence of the DNS records too
Queue rebuild_dns in the discovered host controller (optionally only if pending_dns_record_changes? returns false
Add transient attribute to the NIC or host model (force_dns_rebuild ?), that we can check in Orchestration::DNS.queue_dns and if it is true - queue rebuild_dns

Any thoughts?