Description of problem:
we changed the behavior in 7.7 from duid to mac. Are we missing a rhel7 specific patch?
but in RHEL7.6 in 1.12.0-10 it passed
and in latest z stream too (-14 )
so we need to fix it in RHEL7.7 too
Version-Release number of selected component (if applicable):
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.
> Please, share your opinions.
RHEL-7 must stick to the old default, requiring a downstream patch to revert the change.
(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.
Pushed a downstream patch to RHEL-7.7 NetworkManager repo to preserve the dhcp-client-id default for internal dhcp client.
working rhel7ish again
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.