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 1695723 - [NMCI] ipv4_dhcp_client_id_default_rhel7 test fail
Summary: [NMCI] ipv4_dhcp_client_id_default_rhel7 test fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Francesco Giudici
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 16:56 UTC by Vladimir Benes
Modified: 2019-08-06 13:17 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-1.18.0-0.4.20190408git43d9187c14.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:16:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2302 0 None None None 2019-08-06 13:17:03 UTC

Description Vladimir Benes 2019-04-03 16:56:00 UTC 
Description of problem:
we changed the behavior in 7.7 from duid to mac. Are we missing a rhel7 specific patch?

https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-veth-RHEL-7.7/10/artifact/artifacts/FAIL_report_NetworkManager-ci_Test312_ipv4_dhcp_client_id_default_rhel7.html

but in RHEL7.6 in 1.12.0-10 it passed
http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/03/33948/3394833/6586915/89076896/410701676/report_NetworkManager-ci_Test311_ipv4_dhcp_client_id_default_rhel7.html

and in latest z stream too (-14 )
http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/03/33948/3394838/6586922/89076940/410703027/report_NetworkManager-ci_Test311_ipv4_dhcp_client_id_default_rhel7.html

so we need to fix it in RHEL7.7 too

Version-Release number of selected component (if applicable):
1.18
Comment 3 Francesco Giudici 2019-04-03 17:18:40 UTC 
In the past, the dhcp client id of NetworkManager *internal* dhcp client was managed by the imported systemd code.
So, the dhcp client id for the *internal* dhcp defaulted to RFC 4361 (IAID + DUID): systemd moreover uses a DUID-EN (duid based on an enterprise number), with the enterprise number assigned by IANA to systemd (00:02:00:00:ab:11).

Now we have added DUID management in NM and we have dropped defaulting to systemd DUID (so a default DUID looks different from the past).
Moreover, we defaulted the dhcp-client-id to the mac address of the interface, following what we used to do with the NM default dhcp client: dhclient.

Not sure we want to go back to defaulting to a systemd specific DUID there, as looks wrong to me. I would say "no".
We can discuss instead if we want to default the dhcp-client-id for internal dhcp to RFC 4361 format. I would have a preference for the "no" here too, but don't care that much.

Consider also that internal dhcp on RHEL-7 is NOT the default and that the default one (dhclient) uses MAC addresses.

Please, share your opinions.
Comment 4 Thomas Haller 2019-04-05 10:34:13 UTC 
> Please, share your opinions.

RHEL-7 must stick to the old default, requiring a downstream patch to revert the change.
Comment 5 Vladimir Benes 2019-04-05 12:01:01 UTC 
(In reply to Thomas Haller from comment #4)
> > Please, share your opinions.
> 
> RHEL-7 must stick to the old default, requiring a downstream patch to revert
> the change.

I strongly agree here. Behavior changes are often reported by customers back shortly after we do them.
Comment 6 Francesco Giudici 2019-04-09 13:22:04 UTC 
Pushed a downstream patch to RHEL-7.7 NetworkManager repo to preserve the dhcp-client-id default for internal dhcp client.
Comment 8 Vladimir Benes 2019-04-11 11:06:43 UTC 
working rhel7ish again
Comment 10 errata-xmlrpc 2019-08-06 13:16:46 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, 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-2019:2302
Note You need to log in before you can comment on or make changes to this bug.