Bug 1398836

Summary:	"Cloned Mac" not save
Product:	[Fedora] Fedora	Reporter:	Adam Chasen <adam>
Component:	control-center	Assignee:	Control Center Maintainer <control-center-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	25	CC:	control-center-maint, dcbw, fgiudici, fmuellner, lkundrak, mkasik, ofourdan, rstrode, thaller, tiagomatos
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:16:00 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:

Description Adam Chasen 2016-11-26 14:36:31 UTC

Description of problem:
"Cloned Address" value not saved. Cannot clone MAC address.

Version-Release number of selected component (if applicable):
NetworkManager-1.4.2-1.fc25.x86_64

How reproducible:
Fresh install multiple times

Steps to Reproduce:
1. Network Settings
2. Wired Network
3. Edit
4. Identity
5. Modify "Cloned Address" with validated value (e.g. F6:6C:6B:BD:27:22)
6. Apply
7. Edit again to verify "Cloned Address", was not saved
8. Toggle connection on and off
9. Edit again to verify "Cloned Address", was not saved


Actual results:
Value not saved, MAC address unchanged

Expected results:
Saved value before toggle and MAC address changed after connection toggle


Additional info:

This is on a Chromebox which had the MAC address wiped during bootloader reflashing, so the system sees the built in MAC as AA:BB:CC:DD:EE:FF

This procedure worked on F24

Comment 1 Thomas Haller 2016-11-28 07:31:18 UTC

I assume you are using gnome-control-center to configure the networking?

Reassigning bug...

Comment 2 Adam Chasen 2016-11-28 11:51:57 UTC

That is correct. I was using gnome-control-center

Comment 3 Fedora End Of Life 2017-11-16 18:57:59 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:16:00 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.