Bug 1371623

Summary: fatal failure to set MAC address on wifi
Product: Red Hat Enterprise Linux 7 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.3CC: atragler, bgalvani, daniel, dcbw, extras-qa, fgiudici, hartsjc, lkundrak, lmiksik, lrintel, psimerda, rkhan, thaller, vbenes
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: NetworkManager-1.4.0-8.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1371478 Environment:
Last Closed: 2016-11-03 19:29:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1313485, 1374756    

Description Thomas Haller 2016-08-30 16:13:21 UTC
Some buggy drivers either
 - signal success on the netlink message to change the MAC address, but the
   address only actually change the address a moment later.
 - fail the netlink command with ENFILE but the address actually changes.

See for example upstream https://bugzilla.gnome.org/show_bug.cgi?id=770456 or bug 1371478.

this is fixed upstream with

These workaround should be backported to rhel-7.3

Comment 4 Thomas Haller 2016-09-08 19:14:36 UTC
The fix so far is not sufficient.

Needs another patch from upstream.

Back to assigned

See https://bugzilla.redhat.com/show_bug.cgi?id=1374023#c19

Comment 6 Thomas Haller 2016-09-13 08:40:18 UTC
*** Bug 1374023 has been marked as a duplicate of this bug. ***

Comment 7 Thomas Haller 2016-09-13 08:53:07 UTC
Needs another fix.

See https://bugzilla.redhat.com/show_bug.cgi?id=1374023#c30

Comment 9 Vladimir Benes 2016-09-22 15:20:54 UTC
Reporter verified this workaround works as expected ( https://bugzilla.redhat.com/show_bug.cgi?id=1374023#c30 )

Comment 11 errata-xmlrpc 2016-11-03 19:29:27 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.