Problems with Foreman + dhcp

safranero · December 30, 2019, 11:08am

Hello,

I have a fresh installation of Foreman 1.24 in CentOS 7.7. I followed the instructions of https://www.theforeman.org/manuals/1.24/quickstart_guide.html for CentOS 7 and I hadn’t problems.

I installed dhcp module in puppet with: puppet module install theforeman-dhcp --version 5.1.0

dhcp installed without problems.

I imported the dhcp class and assigned to foreman host.

Problem:
The problem resides when I executed “puppet agent --test”

Expected outcome:
https://pastebin.com/a8qggEaN

Foreman and Proxy versions:

Foreman and Proxy plugin versions:
1.24

Distribution and version:
CentOS 7.7

Other relevant data:

lzap · January 6, 2020, 10:06am

What are you trying to achieve? Foreman itself is managed by our own puppet modules installed from RPM packages. @ekohl

ekohl · January 6, 2020, 11:44am

In the installer we do configure some things for DHCP

github.com

theforeman/puppet-foreman_proxy/blob/master/manifests/proxydhcp.pp

# Configure the DHCP component
class foreman_proxy::proxydhcp {
  # puppet fact names are converted from ethX.X and ethX:X to ethX_X
  # so for alias and vlan interfaces we have to modify the name accordingly
  $interface_fact_name = regsubst($foreman_proxy::dhcp_interface, '[.:]', '_')
  $ip = pick_default($::foreman_proxy::dhcp_pxeserver, fact("ipaddress_${interface_fact_name}"))
  unless ($ip =~ Stdlib::Compat::Ipv4) {
    fail("Could not get the ip address from fact ipaddress_${interface_fact_name}")
  }

  $net  = pick_default($::foreman_proxy::dhcp_network, fact("network_${interface_fact_name}"))
  unless ($net =~ Stdlib::Compat::Ipv4) {
    fail("Could not get the network address from fact network_${interface_fact_name}")
  }

  $mask = pick_default($::foreman_proxy::dhcp_netmask, fact("netmask_${interface_fact_name}"))
  unless ($mask =~ Stdlib::Compat::Ipv4) {
    fail("Could not get the network mask from fact netmask_${interface_fact_name}")
  }

This file has been truncated. show original

It tries to configure a subnet based on an interface. This is because ISC DHCPd will refuse to start up if no subnets have been defined. If you’re managing it by yourself via the ENC, you need to take care of this yourself. The module’s README has some information but that’s mostly focused at writing a profile module. Sadly we also haven’t spent much time at documenting the options.

The short version is that you should use the pools option to define a subnet. The options are name => dhcp::pool. Looking at it, subnet would have been a better name.

Patches to puppet-dhcp are highly welcome, in particular documentation.

safranero · January 8, 2020, 7:45am

Finally, we finished the installation and configuration correctly. The problem resides in configuration of subnet.

Thanks for all.