Bug 1272514 - Anaconda does not save 802.1x network configuration on Fedora Server 22
Summary: Anaconda does not save 802.1x network configuration on Fedora Server 22
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-16 15:30 UTC by Aaron Walker
Modified: 2015-10-16 16:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-16 16:10:51 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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...
Note You need to log in before you can comment on or make changes to this bug.