http://bugzilla.novell.com/show_bug.cgi?id=551310 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c1 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |support@microtechniques.com --- Comment #1 from Michal Zugec 2009-11-06 06:09:35 MST --- Please provide steps to reproduce (it works fine on my machine) and attach yast logs -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 User support@microtechniques.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c3 --- Comment #3 from Don Hughes 2009-11-08 12:23:44 MST --- Created an attachment (id=326173) --> (http://bugzilla.novell.com/attachment.cgi?id=326173) Incorrectly named ifcfg- file -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 User support@microtechniques.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c5 --- Comment #5 from Don Hughes 2009-11-08 12:25:13 MST --- 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). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 User support@microtechniques.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c6 --- Comment #6 from Don Hughes 2009-11-08 12:56:38 MST --- 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. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c8 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kasievers@novell.com --- Comment #8 from Michal Zugec 2009-11-09 03:37:38 MST --- 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? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551310#c10 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kasievers@novell.com --- Comment #10 from Michal Zugec 2009-11-10 06:40:31 MST --- 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) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 http://bugzilla.novell.com/show_bug.cgi?id=551310#c12 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #12 from 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 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551310 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:running:61815:moderat |maint:running:61815:moderat |e |e | |maint:released:sle11-sp3:61 | |916 -- You are receiving this mail because: You are on the CC list for the bug.