Project

General

Profile

Bug #1681

DHCP fails for subnets larger than /24

Added by Ashley Penney almost 7 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

In our environment setting a host to build either fails to add a DHCP entry to dhcpd or leaves incorrect ones behind if the subnet in question is bigger than a /24:

subnet 165.212.8.0 netmask 255.255.248.0 {
option routers 165.212.15.231;
option domain-name "perimeterusa.com";
option domain-name-servers 165.212.12.12;}

We then have a matching entry in foreman.

If we try to build a machine in 165.212.8 it creates the entry.
If we try to build a machine in 165.212.9 it fails to call the proxy to create the entry.

Sometimes we get other behavior like it creating it in .8, then in .10 and not removing the .8 entry in DHCP.

History

#1 Updated by Michael Moll about 2 years ago

  • Description updated (diff)
  • Status changed from New to Resolved

can't imagine this to be a problem anymore

Also available in: Atom PDF