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: