Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStuart Auchterlonie
2015-09-30 23:03:12 UTC
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:
*** Bug 1397518 has been marked as a duplicate of this bug. ***
Comment 11Stephen Benjamin
2018-06-05 13:47:21 UTC
It was recently fixed by someone in the community:
https://github.com/theforeman/puppet-foreman_proxy/pull/422
Once this change makes a Satellite release, you would be able to do this by adding the additional options for network and netmask. For the example in comment #0, this installer command should create a valid DHCP configuration:
satellite-installer --foreman-proxy-dhcp="true" --foreman-proxy-dhcp-interface="eth0" --foreman-proxy-dhcp-range ="10.142.233.5 10.142.233.120" --foreman-proxy-dhcp-gateway="10.142.233.126" --foreman-proxy-dhcp-network="10.142.233.0" --foreman-proxy-dhcp-netmask="255.255.255.128"
Comment 12Satellite Program
2018-06-05 14:15:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222
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: