Bug 1556983

Summary: Ensure the DHCP client-id doesn't change when upgrading from RHEL 7.5
Product: Red Hat Enterprise Linux 7 Reporter: Beniamino Galvani <bgalvani>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.6CC: atragler, bgalvani, fgiudici, jkoten, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:13:09 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:
Attachments:
Description Flags
[dist-git PATCH] dhcp: don't add leading zero to printable client-id none

Description Beniamino Galvani 2018-03-15 16:51:41 UTC 
An inconsistency in client-id sent by different DHCP plugins was fixed upstream [1] and this led to a change in the option content sent by dhclient for textual client-ids.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=793957

I think we want to keep the old behavior on RHEL and so that patch must be reverted if we decide to rebase NM.
Comment 2 Beniamino Galvani 2018-06-20 12:45:39 UTC 
Created attachment 1453212 [details]
[dist-git PATCH] dhcp: don't add leading zero to printable client-id
Comment 3 Thomas Haller 2018-06-20 12:58:40 UTC 
(In reply to Beniamino Galvani from comment #2)
> Created attachment 1453212 [details]
> [dist-git PATCH] dhcp: don't add leading zero to printable client-id

lgtm
Comment 4 Beniamino Galvani 2018-06-20 14:38:17 UTC 
Applied to dist-git.
To do: update CI tests.
Comment 7 errata-xmlrpc 2018-10-30 11:13:09 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-2018:3207