Foreman installer: DHCP proxy issue

Support
1

Hi all,
When installing foreman via the foreman installer the dhcpd.conf file has
invalid parameters set. The following is what is set:

option domain-name-servers option domain-name-servers undef;

This causes issues with ISC. The site of the problem seems to be with foreman_proxy/manifests/proxydhcp.pp:31
and nameservers => [$::ip] It's this value that is undef. Any pointers on
where this variable comes from and/or why it may not be getting set?

Andy

2

That's a temporary variable - it parses for the
$foreman_proxy::dhcp_interface (which defaults to eth0) and then uses
that to get the value of $ipaddress_eth0 (or whatever that variable is
set to). What do you have dhcp_interface set to, and does it show in
Facter's output?

Greg

··· On 4 September 2012 21:37, Andy Edmonds wrote: > Hi all, > When installing foreman via the foreman installer the dhcpd.conf file has > invalid parameters set. The following is what is set: > > option domain-name-servers option domain-name-servers undef; > > This causes issues with ISC. The site of the problem seems to be with > foreman_proxy/manifests/proxydhcp.pp:31 and nameservers => [$::ip] It's > this value that is undef. Any pointers on where this variable comes from > and/or why it may not be getting set?
3

Hey Greg,

I've set:
$dhcp_interface = 'eth1'

Facter reports:

root@foreman:~# facter ipaddress_eth1
192.168.56.2

Andy

··· On 5 Sep 2012, at 00:02, Greg Sutcliffe wrote:

On 4 September 2012 21:37, Andy Edmonds andy.edmonds@gmail.com wrote:

Hi all,
When installing foreman via the foreman installer the dhcpd.conf file has
invalid parameters set. The following is what is set:

option domain-name-servers option domain-name-servers undef;

This causes issues with ISC. The site of the problem seems to be with
foreman_proxy/manifests/proxydhcp.pp:31 and nameservers => [$::ip] It’s
this value that is undef. Any pointers on where this variable comes from
and/or why it may not be getting set?

That’s a temporary variable - it parses for the
$foreman_proxy::dhcp_interface (which defaults to eth0) and then uses
that to get the value of $ipaddress_eth0 (or whatever that variable is
set to). What do you have dhcp_interface set to, and does it show in
Facter’s output?

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

4

Hey Greg,
I was just looking through my DHCP configuration again and noticed that the same issue exists for the PXE boot next server param. In my conf file it's set as:

next-server undef;

It's likely related to the same issue below.

Andy

··· On 5 Sep 2012, at 08:55, Andy Edmonds wrote:

Hey Greg,

I’ve set:
$dhcp_interface = ‘eth1’

Facter reports:

root@foreman:~# facter ipaddress_eth1
192.168.56.2

Andy

On 5 Sep 2012, at 00:02, Greg Sutcliffe greg.sutcliffe@gmail.com wrote:

On 4 September 2012 21:37, Andy Edmonds andy.edmonds@gmail.com wrote:

Hi all,
When installing foreman via the foreman installer the dhcpd.conf file has
invalid parameters set. The following is what is set:

option domain-name-servers option domain-name-servers undef;

This causes issues with ISC. The site of the problem seems to be with
foreman_proxy/manifests/proxydhcp.pp:31 and nameservers => [$::ip] It’s
this value that is undef. Any pointers on where this variable comes from
and/or why it may not be getting set?

That’s a temporary variable - it parses for the
$foreman_proxy::dhcp_interface (which defaults to eth0) and then uses
that to get the value of $ipaddress_eth0 (or whatever that variable is
set to). What do you have dhcp_interface set to, and does it show in
Facter’s output?

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

5

Yes, that'll be the same thing. I've seen this happen when I specify a
non-existant IP, but not seen it happen this way. I'll try and take a
look at it soon(ish) - in the meantime you coud workaround it by
editing the proxydhcp manifest and specifying your requirements
directly. In fact, if you could test that works, that would confirm we
know exactly where the problem is…

Cheers,
Greg

··· On 5 September 2012 09:34, Andy Edmonds wrote: > Hey Greg, > I was just looking through my DHCP configuration again and noticed that the same issue exists for the PXE boot next server param. In my conf file it's set as: > > next-server undef; > > It's likely related to the same issue below. > > Andy
6

Sure will do!
The IP address on eth1 (as specified in params.pp) is configured statically (via /etc/network/interfaces) so it exists at boot.

Andy

··· On 5 Sep 2012, at 11:36, Greg Sutcliffe wrote:

On 5 September 2012 09:34, Andy Edmonds andy.edmonds@gmail.com wrote:

Hey Greg,
I was just looking through my DHCP configuration again and noticed that the same issue exists for the PXE boot next server param. In my conf file it’s set as:

next-server undef;

It’s likely related to the same issue below.

Andy

Yes, that’ll be the same thing. I’ve seen this happen when I specify a
non-existant IP, but not seen it happen this way. I’ll try and take a
look at it soon(ish) - in the meantime you coud workaround it by
editing the proxydhcp manifest and specifying your requirements
directly. In fact, if you could test that works, that would confirm we
know exactly where the problem is…

Cheers,
Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.