Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:2060
Description of problem: After upgrade to "dhclient-4.2.5-68.el7.x86_64", unable to get results on the specifying the "dhcp-client-identifier" Version-Release number of selected component (if applicable): dhclient-4.2.5-68.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure DHCP server: ~~~ # rpm -q dhclient dhclient-4.2.5-68.el7.x86_64 [root@server ~]# cat /etc/dhcp/dhcpd.conf subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.10 192.168.2.20; } host client {option dhcp-client-identifier "client"; fixed-address 192.168.2.15 ; } ~~~ 2. Run "dhclient -I" on the client: ~~~ [root@client ~]# dhclient -I client cant find device client [root@client ~]# rpm -q dhclient dhclient-4.2.5-68.el7.x86_64 ~~~ Actual results: cant find device client Expected results: ~~~ [root@client2 ~]# dhclient -I client [root@client2 ~]# ifconfig enp0s3 enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.2.15 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a00:27ff:fec9:5aff prefixlen 64 scopeid 0x20<link> ether 08:00:27:c9:5a:ff txqueuelen 1000 (Ethernet) RX packets 589 bytes 64494 (62.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 312 bytes 39583 (38.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@client2 ~]# rpm -q dhclient dhclient-4.2.5-36.el7.x86_64 ~~~ Additional info: The man page on the upgraded versions lists two entries for "-I": ~~~ -I <dhcp-client-identifier> Specify the dhcp-client-identifier option to send to the DHCP server. -I Use the standard DDNS scheme from RFCs 4701 & 4702. ~~~