Bug 695262 - yast2 Network Settings deletes configurations for renamed interfaces
yast2 Network Settings deletes configurations for renamed interfaces
: 837476 (view as bug list)
Classification: openSUSE
Product: openSUSE 11.4
Classification: openSUSE
Component: Network
All openSUSE 12.2
: P5 - None : Major (vote)
: ---
Assigned To: Michal Filka
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2011-05-20 20:59 UTC by Don Hughes
Modified: 2021-02-26 20:30 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Don Hughes 2011-05-20 20:59:34 UTC
User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

On a system where the network interface has been renamed from eth0 to Netx you can no longer run yast2 / Network Settings after the most recent 11.4 updates.  If you do the /etc/sysconfig/newtork/ifcfg-Netx is renamed to ifcfg- and the network will no longer start.

This is similar to Bug #551310.

Reproducible: Always

Steps to Reproduce:
1. Install base 11.3 system
2. use yast2 / Network Settings  <edit interface> / Hardware / Device Name / Change to change the network device name from eth0 to Netx
3. Install all current security patches.
4. Upgrade to 11.4 with all current patches
5. Run yast2 / Network Settings

Actual Results:  
Network configuration is deleted.

Expected Results:  
Network configuration is updated.
Comment 2 Marius Tomaschewski 2012-09-27 10:33:03 UTC
BTW: To rename an interface it is required to:
a) ifdown eth0
b) adopt the name in the /etc/udev/rules.d/70-persistent-net.rules,
   e.g. change NAME="eth0" to NAME="Net1" and reload the rules by
   calling "udevadm control --reload-rules".
c) rename ifcfg-eth0 to its new name, e.g. ifcfg-Net1
d) adopt all eth0 references in other files, e.g. SuSEfirewall2 or dhcp
e) rename it at runtime using "ip link set name Net1 dev eth0"
f) ifup Net1
Comment 3 Don Hughes 2012-11-25 16:21:30 UTC
This is still an issue with 12.2

I am using the rename option in yast2 which should handle the manual steps above, or the option should be removed from yast2.
Comment 4 Michal Filka 2013-07-18 12:21:36 UTC
I've tested renaming interfaces in OS 12.3 and it didn't worked.

Tested scenario:
1. change device name for eth0 in Network Settings -> Edit -> Hardware -> Device name to dmz0
2. save changes

it is fixed in:
- yast2-network.rpm 2.25.7
- yast2.rpm 2.24.5

Both packages are under review and will be submitted into factory.
Comment 5 Michal Filka 2013-07-18 12:35:03 UTC
Just to clarify it ...

Failed test (Comment#4) resulted in:
- renamed ifcfg
- updated udev rule

However, existing device wasn't renamed (restart required) and yast was unable to edit renamed interface later on.
Comment 6 Michal Filka 2013-07-22 15:14:28 UTC
Submitted into Factory.
Comment 7 Michal Filka 2013-09-03 09:52:53 UTC
*** Bug 837476 has been marked as a duplicate of this bug. ***
Comment 12 Swamp Workflow Management 2015-05-26 18:00:00 UTC
An update workflow for this issue was started.
This issue was rated as moderate.
Please submit fixed packages until 2015-06-09.
Comment 14 Swamp Workflow Management 2015-06-16 20:05:22 UTC
SUSE-RU-2015:1072-1: An update that has 6 recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 551310,695262,809053,874259,900383,923788
CVE References: 
Sources used:
SUSE Linux Enterprise Software Development Kit 11 SP3 (src):    yast2-, yast2-network-
SUSE Linux Enterprise Server 11 SP3 for VMware (src):    yast2-, yast2-network-
SUSE Linux Enterprise Server 11 SP3 (src):    yast2-, yast2-network-
SUSE Linux Enterprise Desktop 11 SP3 (src):    yast2-, yast2-network-