+++ This bug was initially created as a clone of Bug #1397702 +++ After upgrading to 1.13.1 the DHCP behavior is not consistent: Adding a host successfully retrieves an available IP and inserts a reservation in the leases file Updating a hosts interface values causes a DHCP exception on submit, in the prior version I received an overwrite prompt Deleting a host works without error but the DHCP reservation is not removed from the leases file. This was reported upstream, creating a 6.3 ticket as this is regression in Satellite 6: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-5-configuring-external-services --- Additional comment from RHEL Product and Program Management on 2016-11-23 03:47:09 EST --- Since this issue was entered in Red Hat Bugzilla, the pm_ack has been set to + automatically for the next planned release --- Additional comment from Lukas Zapletal on 2016-12-01 06:02:48 EST --- 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? --- Additional comment from Ohad Levy on 2016-12-01 06:14:05 EST --- 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. --- Additional comment from Stephen Wadeley on 2016-12-05 02:50:28 EST --- 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). = = = = = = Provide a note in https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-5-configuring-external-services to turn off inotify system for DHCP plugin because this will not work via NFS.
Hello lzap I cannot figure out how to do this. Reading the man page suggests this is something down the the C code level. Thank you
Stephen, Which part are you trying to figure out? -d
(In reply to Dmitri Dolguikh from comment #2) > Stephen, > > Which part are you trying to figure out? > > -d How does a user issue a command to turn off inotify for an NFS share. Thank you
There is no way to do this, NFS is not supported at all.
Ohad had this idea of rewriting the chapter for iSCSI instead of NFS. Stephen, are you able to do that yourself? Setting up iSCSI volume is easy (easier than NFS) but we need a heartbeat for HA deployments (that's the hard part). Opening a volume from two clients simultaneously is of course not possible at the block level.
(In reply to Lukas Zapletal from comment #5) > Ohad had this idea of rewriting the chapter for iSCSI instead of NFS. > Stephen, are you able to do that yourself? Yes, but would need a new bug and for the bug to go through the process of assigning: Content Strategist gets a say on priority Documentation Manager assigns the bug to a writer. > Setting up iSCSI volume is easy > (easier than NFS) but we need a heartbeat for HA deployments (that's the > hard part). Opening a volume from two clients simultaneously is of course > not possible at the block level.
(In reply to Dmitri Dolguikh from comment #4) > There is no way to do this, NFS is not supported at all. then this docs bug is NOTABUG ? Or is there something else I am missing?
I don't know why you cloned. The original BZ is the report and we will likely solve this with documentation only changes.
(In reply to Lukas Zapletal from comment #8) > I don't know why you cloned. The original BZ is the report and we will > likely solve this with documentation only changes. I cloned it because I thought you still needed the engineering bug. closing it now