Bug 551310

Summary: Unable to change network device name with yast2
Product: [openSUSE] openSUSE 11.2 Reporter: Don Hughes <support>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: RC 2   
Target Milestone: ---   
Hardware: i386   
OS: openSUSE 11.2   
Whiteboard: maint:released:sle11-sp3:61916
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Deadline: 2015-06-09   
Attachments: yast2 log
Incorrectly named ifcfg- file
yast2 signall file

Description Don Hughes 2009-10-30 11:05:49 UTC
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

If you try to change the network device name (Netwrork Settings -> Hardware -> UdevRules) the network definition is deleted.  Yast appears to be renaming the configuration file under /etc/sysconfig/network from ifcfg-eth0 to ifcfg- (with no suffix).  You can change the name if you do it during the installation process, but not after the system in installed.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Michal Zugec 2009-11-06 13:09:35 UTC
Please provide steps to reproduce (it works fine on my machine) and attach yast logs
Comment 2 Don Hughes 2009-11-08 19:23:08 UTC
Created attachment 326172 [details]
yast2 log
Comment 3 Don Hughes 2009-11-08 19:23:44 UTC
Created attachment 326173 [details]
Incorrectly named ifcfg- file
Comment 4 Don Hughes 2009-11-08 19:24:08 UTC
Created attachment 326174 [details]
yast2 signall file
Comment 5 Don Hughes 2009-11-08 19:25:13 UTC
It does work if the interface is already called something other than eth0.

I change /etc/sysconfig/network/ifcfg-net1 -> ifcfg-eth0

Netwrork Settings -> Hardware -> UdevRules

Note that there is nothing listed under the current device name (it should say eth0).
Change the name.
Select OK and exit.  You do not get any error messages, but when you return to the selection screen, you now have 2 UNconfigured devices.  If you check under /etc/sysconfig/network you will see the file ifcfg-

I will attach 3 files:
1)The yast log
2)The ifcfg- 
3)A signals files (This is probably related to the fact that this was being done remotely and the machine dropped off of the network because of the bad ifcfg- file and had to be rebooted).
Comment 6 Don Hughes 2009-11-08 19:56:38 UTC
The below was how I reproduced the error on a running system.  The error was originally seen be doing the following:

1 ) Do a clean install and leave all of the network setting at their defaults and using DHCP.

2) Log into the the freshly installed system and use yast2 to try and change the device name of eth0 to net1.
Comment 7 Michal Zugec 2009-11-09 08:22:23 UTC
Reproduced. Problem appears when there's no initial record in etc/udev/rules.d/70-persistent-net.rules
Comment 8 Michal Zugec 2009-11-09 10:37:38 UTC
I see 2 problems here:
1 - there's no udev rule in /etc/udev/rules.d/70-persistent-net.rules after installation

2 - changing device name more than once failed without any warning (edit udev rules file and execute "udevadm trigger --subsystem-match=net")

What is supported way to rename device?
Is it possible only once without reboot?
Comment 9 Kay Sievers 2009-11-10 05:07:30 UTC
Interface can only be renamed while they are not in use, I don't know of a way to find out, if they are needed or not. It might work in some cases, but stuff that tries to do that, needs to make sure, that nothing like network servers or VNC, or anything like this is used and needed at the moment. Udev does not support renaming of active interfaces for that reason.
Comment 10 Michal Zugec 2009-11-10 13:40:31 UTC
What about 1. problem? This is also reason of this bugreport (YaST rely on udev that there's always one rule for each device - and this worked in the past)
Comment 11 Kay Sievers 2009-11-10 14:04:07 UTC
Sorry, I have no idea. I don't know of any changes to udev in that area. Does the rule exist after a reboot? Then it's likely that something went wrong during installation.
Comment 12 Michal Zugec 2009-11-20 12:20:25 UTC
It was probably some factory-kernel-issue, after update works again.
Problem with not matching udev rule fixed in yast2-network-2.18.62
Comment 17 Swamp Workflow Management 2015-05-26 17:59:34 UTC
An update workflow for this issue was started.
This issue was rated as moderate.
Please submit fixed packages until 2015-06-09.
https://swamp.suse.de/webswamp/wf/61815
Comment 19 Swamp Workflow Management 2015-06-16 20:05:08 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-2.17.135.1-0.7.1, yast2-network-2.17.199.3-0.7.4
SUSE Linux Enterprise Server 11 SP3 for VMware (src):    yast2-2.17.135.1-0.7.1, yast2-network-2.17.199.3-0.7.4
SUSE Linux Enterprise Server 11 SP3 (src):    yast2-2.17.135.1-0.7.1, yast2-network-2.17.199.3-0.7.4
SUSE Linux Enterprise Desktop 11 SP3 (src):    yast2-2.17.135.1-0.7.1, yast2-network-2.17.199.3-0.7.4