Bug 691785

Summary: Updating NetworkManager breaks manual configured em1
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: dcbw, jklimes
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-02-17 13:42:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Horst H. von Brand 2011-03-29 13:20:33 UTC
Description of problem:
I updates NetworkManager, and my static network configuration for em1 got diconnected. I tried to start it from the nm-applet icon, that didn't work either. Only after a reboot did I get the network back (but now the 'system em1' is preferred over the manual configuration).

Version-Release number of selected component (if applicable):
NetworkManager-0.8.997-6.git20110328.fc15.x86_64

How reproducible:
Happened once, won't/can't try again...

Steps to Reproduce:
1. Update NetworkManager
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dan Williams 2011-04-06 15:50:37 UTC
Can you paste in the  manual connection ifcfg file?

Comment 2 Horst H. von Brand 2011-04-13 00:36:47 UTC
/etc/sysconfig/networking/profiles/default/ifcfg-em1 and /etc/sysconfig/networking/devices/ifcfg-em1 have only the DHCP configuration:

DEVICE="em1"
ONBOOT=yes
NM_CONTROLLED="yes"
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System em1"
UUID=1dad842d-1912-ef5a-a43a-bc238fb267e7
HWADDR=00:26:6C:41:FB:5D
PEERDNS=yes
PEERROUTES=yes
LAST_CONNECT=1300060699

I don't know where NetworkManager stashes away the configurations...

Comment 3 Jirka Klimes 2011-04-13 08:04:42 UTC
NetworkManager uses plugins for reading/writing configuration. The plugins can be configured through /etc/NetworkManager/NetworkManager.conf
e.g:
[main]
plugins=ifcfg-rh

'man NetworkManager.conf' has description of the plugins.

For Fedora/RHEL, ifcfg-rh plugin is used by default. This plugin uses the same configuration files as legacy network/initscrips system. They are /etc/sysconfig/network-scripts/ifcfg-* files. The files in /etc/sysconfig/networking/ are just hard links used by system-config-network tool to handle profiles.

The file you pasted is correct configuration for DHCP ethernet. However, I'm not sure I quite understand the actual problem. By saying 'static' or 'manual', do you want to say you had your IP manually/statically configured and that NetworkManager changed it to DHCP?

Comment 4 Horst H. von Brand 2011-04-17 15:26:25 UTC
(In reply to comment #3)
> The file you pasted is correct configuration for DHCP ethernet. However, I'm
> not sure I quite understand the actual problem. By saying 'static' or 'manual',
> do you want to say you had your IP manually/statically configured and that
> NetworkManager changed it to DHCP?

I had configured the interface (via NetworkManager's applet in my account) to use a static configuration (at work there is no DHCP, need to change that BTW...). The update broke that setup.

Comment 5 Fedora End Of Life 2013-04-03 14:22:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 6 Fedora End Of Life 2015-01-09 16:37:40 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 7 Fedora End Of Life 2015-02-17 13:42:18 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.