Bug 128823

Summary:	Cloning system messes network config up
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Felix Möller <felix>
Component:	Network	Assignee:	Christian Zoz <zoz>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	aj, felix, hare
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Fixes the error messages

Description Felix Möller 2005-10-17 20:04:35 UTC

We are using SuSE 10.0 in an educational environment.  To keep administration
work low, we install on one client and clone the whole system with udpcast[1] to
all other clients. (same hardware)

With former SuSE releases one was able to rename
/etc/sysconfig/network/ifcfg-eth-id-<mac> to ifcfg-eth0 and the cloned system
would work with it. 

Now with SuSE 10, this does not work the devices are named eth1, this is caused
by /etc/udev/rules.d/30-net_persistent_names.rules this file renames the devices.  

For now we are just deleting this file, but is this the right[tm] way to go?

Another thing that came up dealing with this is, that somehow the
/etc/init.d/network is coming to a "cat /sys/class/net/eth0/ifindex".
Therefore a lot of error messages like:
"cat: /sys/class/net/eth0/ifindex: No such file or directory" are shown.
I do not have access to the system right now, but if necessary I could
investigate this more.
Should I open another bug report for this?!

fm
[1] - http://udpcast.linux.lu/

Comment 1 Christian Zoz 2005-10-18 10:05:34 UTC

The first issue is not a bug, but a support request. Try autoyast.
The second might be a bug.

You can delete /etc/udev/rules.d/30-net_persistent_names.rules always. The worst
things that might happen is that your interface names change (if there are more
then one). It will again create this file, but with interface names starting at 0.
So rename ifcfg- and delete 30-net* in your clone image and all will be fine.
Don't delete /etc/udev/rules.d/31-net_create_names.rules.

The second issue seems to be a result of having a config ifcfg-eth0 but no
interface eth0. I will check that.

Comment 2 Felix Möller 2005-10-20 10:14:44 UTC

Thanks for your reply.

I just have access to the machine and thought it might be helpful to copy the output:

    eth1      device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
    eth1      (DHCP) . . . . . <notice>pidofproc: dhcpcd 4212
IP/Netmask: 192.168.1.104 / 255.255.255.0 ('hs04') 
doneWaiting for mandatory devices:  eth0
15 14 cat: /sys/class/net/eth0/ifindex: No such file or directory
12 cat: /sys/class/net/eth0/ifindex: No such file or directory
11 cat: /sys/class/net/eth0/ifindex: No such file or directory
10 cat: /sys/class/net/eth0/ifindex: No such file or directory
9 cat: /sys/class/net/eth0/ifindex: No such file or directory
8 cat: /sys/class/net/eth0/ifindex: No such file or directory
7 cat: /sys/class/net/eth0/ifindex: No such file or directory
6 cat: /sys/class/net/eth0/ifindex: No such file or directory
5 cat: /sys/class/net/eth0/ifindex: No such file or directory
4 cat: /sys/class/net/eth0/ifindex: No such file or directory
3 cat: /sys/class/net/eth0/ifindex: No such file or directory
2 cat: /sys/class/net/eth0/ifindex: No such file or directory
1 cat: /sys/class/net/eth0/ifindex: No such file or directory
0 cat: /sys/class/net/eth0/ifindex: No such file or directory

The net directory contains:
# ls /sys/class/net/
.  ..  eth1  lo  sit0

HTH
fm

Comment 3 Christian Zoz 2005-10-24 11:47:42 UTC

Created attachment 55189 [details]
Fixes the error messages

This patch makes rcnetwork not to gather the existence of an interface from the existence of a ifcfg-<interface> file.

Comment 4 Christian Zoz 2005-10-24 11:48:59 UTC

Patch added to svn