Bug 1397702

I reported this based on upstream report: http://projects.theforeman.org/issues/17301#note-12

This is a regression introduced by inotify thing in DHCP module, I think the inotify should have been configurable from the day one. User can choose if they want better performance or HA (which can be slow over NFS).

How we should handle this, Ohad?

As for now, the workaround for HA (with Satellite version 6.3) should entail using a block volume (such as iscsi) instead with only one master in RW mode.

I will clone for the Installation Guide (the Doc Text field in Engineering bugs is for use in Errata and Release Notes, the guides need their own bug).

(In reply to Stephen Wadeley from comment #4)
> I will clone for the Installation Guide (the Doc Text field in Engineering
> bugs is for use in Errata and Release Notes, the guides need their own bug).

The documentation update has been made within bug 1378551 as per comment https://bugzilla.redhat.com/show_bug.cgi?id=1378551#c23.

There's now a dedicated module for handling remote dhcpd setups: https://github.com/theforeman/smart_proxy_dhcp_remote_isc. It's been packaged and is available from 1.15 and nightly foreman yum repositories.

Correct, that's the fix to use in downstream.

AFAIK the only thing that is missing is support for dhcp_remote_isc provider in the installer.

Turns out I added a puppet module for the installer when I created the provider: https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/plugin/dhcp/remote_isc.pp

I believe all the required work landed upstream. We need just pull the packages downstream. Moving to MODIFIED.

NI on Dmitri as Ivan is on PTO.

By "the packages" Ivan means "rubygem-smart_proxy_dhcp_remote_isc", that's the only package needed, right?

Ivan probably means that rubygem-smart_proxy_dhcp_remote_isc and corresponding changes to the proxy puppet module are available upstream.

Ok, we already have the needed installer changes downstream, so let's pull in rubygem-smart_proxy_dhcp_remote_isc and see how it goes. Thanks!

Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1489364 for dhcp module documentation changes.

FYI: I've found potential issues with packaging in https://bugzilla.redhat.com/show_bug.cgi?id=1535972 + some additional issues that need some additional debugging in https://bugzilla.redhat.com/show_bug.cgi?id=1489364#c21

Build: Satellite 6.3.0 snap35

Satellite is configured with external DHCP and remote_isc as provider.

A host is provisioned through satellite.  
[root@localhost dhcpd]# cat dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.2.5

server-duid "\000\001\000\001\"\014\221O\000\032J>\246P";

host cindy-beiser.domain {
  dynamic;
  hardware ethernet 00:1a:4a:3e:a6:51;
  fixed-address 10.AA.AA.236;
        supersede server.filename = "pxelinux.0";
        supersede server.next-server = 0a:08:72:01;
        supersede host-name = "cindy-beiser.domain";
}

Tried to update the Host inerface ip from UI, I got a conflict wizard , but on clicking override , I was able to update the Ip of the Host.

[root@localhost dhcpd]# cat dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.2.5

server-duid "\000\001\000\001\"\014\221O\000\032J>\246P";

host cindy-beiser.domain {
  dynamic;
  hardware ethernet 00:1a:4a:3e:a6:51;
  fixed-address 10.AA.AA.237;
        supersede server.filename = "pxelinux.0";
        supersede server.next-server = 0a:08:72:01;
        supersede host-name = "cindy-beiser.domain";
}

On Deleting the said host, the dhcpd.leases file is update with a new record for host as deleted , but I can still see the old record , Is this intended ?
cat dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.2.5

server-duid "\000\001\000\001\"\014\221O\000\032J>\246P";

host cindy-beiser.domain {
  dynamic;
  hardware ethernet 00:1a:4a:3e:a6:51;
  fixed-address 10.AA.AA.237;
        supersede server.filename = "pxelinux.0";
        supersede server.next-server = 0a:08:72:01;
        supersede host-name = "cindy-beiser.domain";
}
host cindy-beiser.domain {
  dynamic;
  deleted;
}

Host record is only marked as "deleted" on delete, and will be removed from the leases file next time dhcpd persists its in-memory database to disk.

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