Project

General

Custom queries

Profile

Actions
Copy link

Bug #1567

closed

Foreman-proxy ignores "include" directive in dhcpd.conf

Added by Leszek Szarlej about 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Mikael Fridh
Category:
DHCP
Target version:
1.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi,

With the following line in the dhcpd.conf foreman-proxy is not importing subnets defined in included file.

include "/etc/dhcpd.conf.subnets";

The file has a proper permissions allowing foreman-proxy to read the file. No errors in foreman-proxy during the import action:

D, [2012-04-04T07:54:38.783583 #6857] DEBUG -- : Loading subnets for 127.0.0.1
D, [2012-04-04T07:54:38.783727 #6857] DEBUG -- : Added 192.168.97.0/255.255.255.0 to 127.0.0.1

Info on the screen:
"No new subnets found"

I am not sure whether it's a bug or "by design". I am testing foreman against large installation where this feature would be much appriciated.
thanks
L.

Added by Mikael Fridh almost 13 years ago

Revision fcf097c2 (diff)

fixes #1567 - Foreman-proxy ignores dhcpd.conf include directive

Adding functionality that can detect and parse included files in dhcpd.conf.
Supports same syntax as dhcpd.conf(5) manual page specifies on the include
statement:

include "filename";
The include statement is used to read in a named file, and
               process the contents of that file as though it were entered in
               place of the include statement.

This parsing currently requires (unlike isc-dhcpd) that the include statement
is on it's own line, preceded by optional whitespace.

Added by Ohad Levy about 12 years ago

Revision f3923961 (diff)

refs #1567 - fixed a copy paste error

Actions
Copy link

Also available in: Atom PDF