Created attachment 56996 [details]
YaST2 logs

Please don't compress or tar logfiles. Only the most recent logfile is required here. Always attach them as plain text, this makes handling much easier.

Please attach the output of `hwinfo --network' either.

098088:/home/michael # hwinfo --network
24: None 01.0: 10701 Ethernet
  [Created at net.111]
  UDI: /org/freedesktop/Hal/devices/net_00_13_d4_bc_1d_55
  Unique ID: L2Ua.ndpeucax6V1
  Parent ID: JNkJ.Buw2ZJWujl6
  SysFS ID: /class/net/eth1
  SysFS Device Link: /devices/pci0000:00/0000:00:0a.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "forcedeth"
  Device File: eth1
  HW Address: 00:13:d4:bc:1d:55
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #10 (Ethernet controller)

25: None 00.0: 10700 Loopback
  [Created at net.111]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

26: None 00.0: 10781 Network Interface
  [Created at net.111]
  Unique ID: wl2P.nfEXJulusj6
  SysFS ID: /class/net/sit0
  Hardware Class: network interface
  Model: "Network Interface"
  Device File: sit0
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Reassigned.

See /etc/udev/rules.d/30-net_persistent_names.rules
We have a feature request to make this editable by yast already.

IMHO this doesn´t need to be made editable, but if I remove a network device from YaST (what I did with the old network interface) of course the rule should be removed. This was not the case here so this is a bug, or am I wrong here?

It is a missing feature - yast does not know about udev rules currently.
I need to find a reference to the feature.

/usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names

We got the same problem. If we choose the same static IP-Adress as before in the deletet Interface, YAST sais that this IP-Adress is already in use.

It would be helpful, just to know how to manually reset all the network interface configuration.

Solution for us (the installation is used on a server and hardware will not be changed):
in /etc/sysconfig/network/config
set FORCE_PERSISTANT_NAMES=no

IMO this is a bug design flaw in SuSE (fortunately the only one), I´ve written many bug reports about this (if removing hardware the previous state isn´t restored, so you run into troble when changing the hardware) but nobody seems to care really. Perhaps after 10.1 release somebody will think about this :)

This is a wanted feature. There are hotpluggable devices and you want the same interface name every time you plug the same device.
If you replace a device permanently, you get eth1 (or higher) instead of eth0. But that is not a problem. Just get used to the fact that a single netiface need not always be named eth0. That's all.
And as Markus wrote in comment 10 you can switch that off with 
FORCE_PERSISTANT_NAMES=no if you don't like that.

All we should change is that we remove also the udev rule if the interface config is removed.

In the other bug reports I´ve written exactly that. For hotpluggable devices the device entry in stays, and so does the config. But when I remove a device (regardless of kind) in YaST it should remove:

1. The sysconfig settings (is done now)
2. The udev rules if appropriate (missing)
3. The /etc/modprobe.d/* file (missing)
4. The /var/udi hotplug file (missing)

Reassigning to the new maintainer of yast2-network.

*** This bug has been marked as a duplicate of bug 145001 ***