RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1354575 - Client-Hostname option not syncing in secondary server's dhcp.leases file
Summary: Client-Hostname option not syncing in secondary server's dhcp.leases file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dhcp
Version: 7.2
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Pavel Zhukov
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1380362 1393869
TreeView+ depends on / blocked
 
Reported: 2016-07-11 15:29 UTC by SHAURYA
Modified: 2020-06-11 12:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-19 06:31:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description SHAURYA 2016-07-11 15:29:19 UTC 
Description of problem: Client-Hostname option not syncing in secondary server's dhcp.leases file

dhcpd.leases file primary
lease 10.12.202.96 {
  starts 4 2016/06/09 08:44:10;
  ends 4 2016/06/09 08:44:20;
  tstp 4 2016/06/09 14:44:15;
  tsfp 4 2016/06/09 14:44:15;
  atsfp 4 2016/06/09 14:44:15;
  cltt 4 2016/06/09 08:44:10;
  binding state active;
  next binding state expired;
  hardware ethernet 00:1a:xx:xx:xx:xx;
  uid "\001\000\032\350\207@\252";
  client-hostname "xxxx";
}

dhcpd.leases file secondary
lease 10.12.202.96 {
  starts 4 2016/06/09 08:44:10;
  ends 4 2016/06/09 08:44:20;
  tstp 4 2016/06/09 08:41:10;
  tsfp 4 2016/06/09 14:44:15;
  atsfp 4 2016/06/09 14:44:15;
  cltt 4 2016/06/09 08:29:34;
  binding state active;
  next binding state expired;
  hardware ethernet 00:1a:xx:xx:xx:xx;
  uid "\001\000\032\350\207@\252";
}

So as one can see the option doesn't sync automatically. But when the dhcp.leases file is renamed on secondary server and service is restarted on both the server the option syncs. But again when a new client gets an IP address it doesn't sync.


Version-Release number of selected component (if applicable): dhcp-4.2.5-42.el7.x86_64


How reproducible: Everytime


Steps to Reproduce:
1. Create a DHCP primary and secondary server
2. Allow clients to get an IP from primary dhcp server and check dhcp.leases file. Depending on client it might send client-hostname option and might not. If it is there then check dhcp.leases file on secondary server
3.The secondary dhcp server will have all the lease informatioon except client-hostname option in it

Actual results: client-hostname option not syncing in secondary dhcp server's dhcp.leases file


Expected results: client-hostname option should also sync along with all other lease info on secondary dhcp server's dhcp.leases file. 


Additional info:

Please check these forums. They are having same issue.

https://lists.isc.org/pipermail/dhcp-users/2009-February/008432.html
https://forum.pfsense.org/index.php?topic=81711.0
Comment 20 Pavel Zhukov 2017-05-19 06:31:46 UTC 
In current implementation neither ddns nor request options are being sent to the peer [1][2]. It's not good but not a bug by itself. RFC (draft) doesn't require it either. So the problem most likely in client not sending option 12 in DHCPREQUEST. On the other hand it's not mandatory. 

As it's only visibility issue (no real harm for users) I'm closing this bug report.

[1]
dhcp/server/failover.c::isc_result_t%20dhcp_failover_send_bind_update

&skip_failover_option,	/* XXX DDNS */
&skip_failover_option,	/* XXX request options */
&skip_failover_option,	/* XXX reply options */

[2]
(bndupd (client-last-transaction-time<8> 1494919278)
 (start-time-of-state<8> 1494919278)
 (potential-expiration-time<8> 1494919368)
 (lease-expiration-time<8> 1494919338)
 (client-hardware-address<11> 1 178 227 166 117 133 110)
 (binding-status<5> 2) (assigned-IP-address<8> 192.168.78.144)
)


[3] http://www.networksorcery.com/enp/protocol/bootp/option012.htm
Note You need to log in before you can comment on or make changes to this bug.