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.

Bug 1943153

Summary: [RFE] Add granting DHCP server to stored DHCP lease information
Product: Red Hat Enterprise Linux 8 Reporter: Nate <nlager>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Matej Berezny <mberezny>
Severity: medium Docs Contact: Mayur Patil <maypatil>
Priority: medium    
Version: 8.3CC: acardace, bgalvani, ferferna, fge, lrintel, maypatil, mberezny, mmatsuya, rkhan, sukulkar, till, vbenes
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.39.3-1.el8 Doc Type: Enhancement
Doc Text:
.NetworkManger now stores DHCP lease information in the `/run/NetworkManager/devices/` directory NetworkManager now stores lease information from the DHCP server in the `/run/NetworkManager/devices/` directory. Previously, the file-based API was not available and this information was only visible in the output of the `nmcli -f all devices show DEVICE` command. With this enhancement, other utilities and scripts can access DHCP options without calling `nmcli`.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 10:07:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nate 2021-03-25 13:32:42 UTC
Description of problem:
NetowrkManager does not log or display information about what DHCP server granted its lease.  This information was provided by dhclient when it was the standard.

Version-Release number of selected component (if applicable):
RHEL 8.3, NetworkManager-1.26.0-13.el8_3.src.rpm

How reproducible:
Every Time

Steps to Reproduce:
Attain DHCP lease
Attempt to discern what server provided said lease using nmcli conn show <interface> OR view stored lease file


Actual results:
No granting dhcp server is listed in dhcp lease options.
No log in system journal or syslog shows this information either.

Expected results:
This information should be available from one, or several, of the sources listed above.

Comment 16 errata-xmlrpc 2022-11-08 10:07:31 UTC
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 (NetworkManager bug fix and enhancement update), 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/RHBA-2022:7680