Bug 1267766 - capsule installer generates invalid dhcp.conf for non local networks
capsule installer generates invalid dhcp.conf for non local networks
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Installer (Show other bugs)
6.1.2
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: Triaged
: 1397518 (view as bug list)
Depends On:
Blocks: 1317008
  Show dependency treegraph
 
Reported: 2015-09-30 19:03 EDT by Stuart Auchterlonie
Modified: 2017-07-28 01:53 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2129691 None None None 2016-01-19 04:40 EST
Foreman Issue Tracker 16949 None None None 2016-10-14 10:32 EDT

  None (edit)
Description Stuart Auchterlonie 2015-09-30 19:03:12 EDT
Description of problem:

Customer has a network setup as follows

<build_network> -- <dhcp_relay> -- <capsule>

The build network is in one subnet, and
the network infrastructure relays the dhcp
request to the capsule on another subnet.

The capsule has no interface in the subnet
used via the build network.

Capsule ip 10.140.13.67/24, interface eth0
Build network - 10.142.233.0/25

When you specify the ip ranges that are used
by the build network to capsule installer
it generates an invalid dhcp.conf file,
by defining the subnet based upon the interface
being given, and the pool range from the dhcp range
being provided

Version-Release number of selected component (if applicable):

Sat 6.1.2

How reproducible:

100%

Steps to Reproduce:
1. Run capsule installer with the following options in addition to 
   those usually required to install a capsule
   --dhcp                 "true"
   --dhcp-interface       "eth0"
   --dhcp-range "10.142.233.5 10.142.233.120"
   --dhcp-gateway "10.142.233.126"
2.
3.

Actual results:

Generate dhcp.conf is contains the following invalid stanza

~~~
subnet 10.140.13.0 netmask 255.255.255.0 {
  pool
  {
    range 10.142.233.5 10.142.233.120;
  }

  option subnet-mask 255.255.255.0;
  option routers 10.142.233.126;
}
~~~

As the pool range is outside of the subnet range
dhcpd throws an error

Expected results:

The pool range should be correctly defined within
the appropriate subnet stanza.

Additional info:
Comment 2 Bryan Kearney 2016-07-26 11:25:24 EDT
Moving 6.2 bugs out to sat-backlog.
Comment 3 Bryan Kearney 2016-07-26 11:40:12 EDT
Moving 6.2 bugs out to sat-backlog.
Comment 5 Stephen Benjamin 2016-10-14 10:32:04 EDT
Created redmine issue http://projects.theforeman.org/issues/16949 from this bug
Comment 6 Stephen Benjamin 2016-11-22 14:13:38 EST
*** Bug 1397518 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.