Bugzilla – Bug 695262
yast2 Network Settings deletes configurations for renamed interfaces
Last modified: 2021-02-26 20:30:05 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.
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
Network configuration is deleted.
Network configuration is updated.
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
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.
I've tested renaming interfaces in OS 12.3 and it didn't worked.
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.
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.
Submitted into Factory.
*** Bug 837476 has been marked as a duplicate of this bug. ***
An update workflow for this issue was started.
This issue was rated as moderate.
Please submit fixed packages until 2015-06-09.
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
SUSE Linux Enterprise Software Development Kit 11 SP3 (src): yast2-126.96.36.199-0.7.1, yast2-network-188.8.131.52-0.7.4
SUSE Linux Enterprise Server 11 SP3 for VMware (src): yast2-184.108.40.206-0.7.1, yast2-network-220.127.116.11-0.7.4
SUSE Linux Enterprise Server 11 SP3 (src): yast2-18.104.22.168-0.7.1, yast2-network-22.214.171.124-0.7.4
SUSE Linux Enterprise Desktop 11 SP3 (src): yast2-126.96.36.199-0.7.1, yast2-network-188.8.131.52-0.7.4