Bug 1267766
| Summary: | capsule installer generates invalid dhcp.conf for non local networks | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Stuart Auchterlonie <sauchter> |
| Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.2 | CC: | bkearney, mschwabe, nshaik, pcfe, pcreech, stbenjam, tonay |
| Target Milestone: | 6.5.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:36:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1317008 | ||
Moving 6.2 bugs out to sat-backlog. Moving 6.2 bugs out to sat-backlog. Created redmine issue http://projects.theforeman.org/issues/16949 from this bug *** Bug 1397518 has been marked as a duplicate of this bug. *** 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" Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16949 has been resolved. Thanks, Stephen, for providing this. Cheers, Michael Verified on Satellite 6.5 snap 21, satellite-installer configures dhcp correctly in capsule scenario using --forema-proxy-dhcp* options 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: