Description of problem: In Satellite 6.3, there should be a possibility to use an alternative implementation of the DHCP ISC provider that can work with NFS shares. However, it's not possible to enable it, probably due to missed cherry-pick of https://github.com/theforeman/foreman-installer/commit/998473290d6cd707caec3c374c5d3c2604e4d3e2 See also https://bugzilla.redhat.com/show_bug.cgi?id=1489364#c21
Build: Satellite 6.3.0 snap3 I was able to configure external DHCP and share the config files via NFS and configure satellite to use it. satellite-installer --foreman-proxy-dhcp=true --foreman-proxy-dhcp-provider=remote_isc --foreman-proxy-plugin-dhcp-remote-isc-dhcp-config /mnt/nfs/etc/dhcp/dhcpd.conf --foreman-proxy-plugin-dhcp-remote-isc-dhcp-leases /mnt/nfs/var/lib/dhcpd/dhcpd.leases --foreman-proxy-plugin-dhcp-remote-isc-key-name=omapi_key --foreman-proxy-plugin-dhcp-remote-isc-key-secret=TpN52jHscfGyo9d+u8RvrH+vGYwNo4Nfw6ihzsn57BF6NhJrB43cuEMxUZJ7X3GocQKvpzrtetXld3lBeY59iQ== --foreman-proxy-plugin-dhcp-remote-isc-omapi-port=7911 --enable-foreman-proxy-plugin-dhcp-remote-isc --foreman-proxy-dhcp-server=External server Installing Done [100%] [................................................................................................................................] Success! * Satellite is running at https://sat-host * To install an additional Capsule on separate machine continue by running: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar" * To upgrade an existing 6.2 Capsule to 6.3: Please see official documentation for steps and parameters to use when upgrading a 6.2 Capsule to 6.3. The full log is at /var/log/foreman-installer/satellite.log I was successfully able to provision a box from satellite, and it got ip from the external dhcp I, [2018-02-06T11:44:00.094974 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:44:00 -0500] "GET /dhcp/10.8.XXX.0/unused_ip HTTP/1.1" 200 20 2.0569 I, [2018-02-06T11:44:30.007991 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:44:30 -0500] "GET /version HTTP/1.1" 200 234 0.0007 I, [2018-02-06T11:47:05.370723 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:05 -0500] "GET /dhcp/10.8.XX.0/unused_ip HTTP/1.1" 200 21 2.0295 I, [2018-02-06T11:47:46.936166 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:46 -0500] "GET /tftp/serverName HTTP/1.1" 200 71 0.0009 I, [2018-02-06T11:47:47.053037 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /dhcp/10.8.XX.0 HTTP/1.1" 200 - 0.0581 I, [2018-02-06T11:47:47.123467 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /dns/ HTTP/1.1" 200 - 0.0507 I, [2018-02-06T11:47:47.180215 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /dns/ HTTP/1.1" 200 - 0.0412 I, [2018-02-06T11:47:47.382080 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /tftp/PXELinux/00:1a:4a:3e:a6:51 HTTP/1.1" 200 - 0.0019 I, [2018-02-06T11:47:47.422178 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0071 I, [2018-02-06T11:47:47.439406 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:47:47 -0500] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0020 E, [2018-02-06T11:48:56.508944 ] ERROR -- : Attempt to remove nonexistent client certificate for cindy-beiser.sat-domain I, [2018-02-06T11:48:56.509670 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:48:56 -0500] "DELETE /puppet/ca/cindy-beiser.sat-domain HTTP/1.1" 404 95 1.2277 I, [2018-02-06T11:48:56.642003 ] INFO -- : 127.0.0.1 - - [06/Feb/2018:11:48:56 -0500] "POST /puppet/ca/autosign/cindy-beiser.sat-domain HTTP/1.1" 200 - 0.0008 External DHCP: Feb 6 11:48:03 localhost dhcpd: DHCPDISCOVER from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:03 localhost dhcpd: DHCPOFFER on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:06 localhost dhcpd: DHCPDISCOVER from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:06 localhost dhcpd: DHCPOFFER on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:14 localhost dhcpd: Dynamic and static leases present for 10.X.XX.236. Feb 6 11:48:14 localhost dhcpd: Remove host declaration cindy-beiser.sat-domain or remove 10.X.XX.236 Feb 6 11:48:14 localhost dhcpd: from the dynamic address pool for 10.X.XX.0/24 Feb 6 11:48:14 localhost dhcpd: DHCPREQUEST for 10.X.XX.236 (10.X.XX.2) from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:14 localhost dhcpd: DHCPACK on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:40 localhost dhcpd: DHCPDISCOVER from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:40 localhost dhcpd: DHCPOFFER on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:40 localhost dhcpd: Dynamic and static leases present for 10.X.XX.236. Feb 6 11:48:40 localhost dhcpd: Remove host declaration cindy-beiser.sat-domain or remove 10.X.XX.236 Feb 6 11:48:40 localhost dhcpd: from the dynamic address pool for 10.X.XX.0/24 Feb 6 11:48:40 localhost dhcpd: DHCPREQUEST for 10.X.XX.236 (10.X.XX.2) from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:48:40 localhost dhcpd: DHCPACK on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: Dynamic and static leases present for 10.X.XX.236. Feb 6 11:49:09 localhost dhcpd: Remove host declaration cindy-beiser.sat-domain or remove 10.X.XX.236 Feb 6 11:49:09 localhost dhcpd: from the dynamic address pool for 10.X.XX.0/24 Feb 6 11:49:09 localhost dhcpd: DHCPREQUEST for 10.X.XX.236 from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: none: host unknown. Feb 6 11:49:09 localhost dhcpd: DHCPACK on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: DHCPDISCOVER from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: DHCPOFFER on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: Dynamic and static leases present for 10.X.XX.236. Feb 6 11:49:09 localhost dhcpd: Remove host declaration cindy-beiser.sat-domain or remove 10.X.XX.236 Feb 6 11:49:09 localhost dhcpd: from the dynamic address pool for 10.X.XX.0/24 Feb 6 11:49:09 localhost dhcpd: DHCPREQUEST for 10.X.XX.236 (10.X.XX.2) from 00:1a:4a:3e:a6:51 via eth0 Feb 6 11:49:09 localhost dhcpd: DHCPACK on 10.X.XX.236 to 00:1a:4a:3e:a6:51 via eth0
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-2018:0336