Bug 1272514

Summary:	Anaconda does not save 802.1x network configuration on Fedora Server 22
Product:	[Fedora] Fedora	Reporter:	Aaron Walker <aaron>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	22	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-16 16:10:51 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 Aaron Walker 2015-10-16 15:30:58 UTC

Description of problem:

During Installation of Fedora server 22, the network is set up with the Graphical installer, and proceeds to work. After reboot, the 802.1x settings are not saved

Version-Release number of selected component (if applicable):


How reproducible:

Tried twice - Failed both times

Steps to Reproduce:

1. Install Fedora as normal
2. Configure network to use 802.1x using PEAP
3. Reboot system after installation 

Actual results:

The settings for the 802.1x configuration are not saved, other elements, such as host name are

Expected results:

The network should work, and the 802.1x settings should have been saved

Additional info:

Maybe due to lack of support for 802.1x in nmcmd? - Just an idea...