Bug 983238
| Summary: | Network configuration does not show new settings | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Hamzy <hamzy> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, rvykydal, sbueno, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-26 15:02:45 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
Mark Hamzy
2013-07-10 19:15:28 UTC
Can you be more specific? Note that the main screen displays current active device configuration. With "Configure", Connection Editor is run which just modifies saved configuration (connection) for the device. To apply the modified configuration, the connection/device has to be switched off and on. Does it explain your case? Huh. So the user clicks configure, edits the network connection, and then clicks save. Do you really expect the user to click Off and then click On just to see the new configuration that had already been previously saved? So, here is a usage scenario. System has two network cards. When the system boots up, dhcp is used to give two temporary addresses. However, this system has two network addresses (and hostnames) already reserved. They just were not specified on the boot command line. The network cards can be configured in the "Network Configuration" page. However, the information is not shown immediately after save. (In reply to Mark Hamzy from comment #2) > Huh. > > So the user clicks configure, edits the network connection, and then clicks > save. Do you really expect the user to click Off and then click On just to > see the new configuration that had already been previously saved? > You need to switch the connection off and on to apply the saved configuration to the device. This is how Gnome desktop network config interface (gnome-control-center) used to work as well in times when using NM Connection Editor. However, in F19, there is native g-c-c interface that seems to apply the configuration right away instead of just saving it (there is [Apply] button vs. [Save] button in Connection Editor). Long term goal is to have common network configuration UI for Desktop and installer. A large shared part used to be Connection Editor in F18 and earlier. Unfortunately, unlike Connection Editor (which has its issues too) the new g-c-c UI seems to be hard to impossible to integrate into installer reasonably so desktop is drawing apart again... > So, here is a usage scenario. System has two network cards. When the > system boots up, dhcp is used to give two temporary addresses. However, > this system has two network addresses (and hostnames) already reserved. > They just were not specified on the boot command line. The network cards > can be configured in the "Network Configuration" page. However, the > information is not shown immediately after save. Because it has not been applied, the current device configuration remains shown. This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20 *** This bug has been marked as a duplicate of bug 1018471 *** |