Bug 1516659

Summary: [NMCI] bridge_set_mac_var1 failed
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: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: atragler, bgalvani, fgiudici, lmiksik, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.10.2-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 13:34:16 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 Beniamino Galvani 2017-11-23 08:37:02 UTC
Scenario: nmcli - bridge - set mac address via two properties

* Add a new connection of type " bridge " and options " con-name br12 ifname br12 autoconnect no ethernet.cloned-mac-address 02:02:02:02:02:02 "

* Check ifcfg-name file created for connection " br12 "

* Open editor for connection " br12 "

* Set a property named " bridge.mac-address " to " f0:de:aa:fb:bb:cc " in editor

* Save in editor

* Check value saved message showed in editor

* Quit editor

* Bring up connection " br12 " ignoring error

Then " ether 02:02:02:02:02:02 " is visible with command " ip a s br12 "

Assertion Failed: pattern ether 02:02:02:02:02:02 is not visible with ip a s br12

Comment 2 Beniamino Galvani 2017-11-23 09:19:37 UTC
Please review branch bg/ifcfg-rh-bridge-mac-rh1516659.

Comment 3 Thomas Haller 2017-11-23 16:25:40 UTC
(In reply to Beniamino Galvani from comment #2)
> Please review branch bg/ifcfg-rh-bridge-mac-rh1516659.

lgtm

Comment 6 Vladimir Benes 2018-01-15 09:52:26 UTC
Test passing again since November.

Comment 9 errata-xmlrpc 2018-04-10 13:34:16 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:0778