Bug ID | 903582 |
---|---|
Summary | net-udev rules no longer applied in 13.2 |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | 13.2 RC 1 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | AutoYaST |
Assignee | autoyast-maintainers@suse.de |
Reporter | bos@je-eigen-domein.nl |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
We use autoyast templates with a static network configuration like: == <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr><?=$ip ?></ipaddr> <netmask><?=$netmask ?></netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway><?=$gateway ?></gateway> <netmask>-</netmask> </route> </routes> </routing> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value><?=$mac ?></value> </rule> </net-udev> == Works fine with OpenSuse 13.1 But the net-udev part is broken in OpenSuse 13.2 There is no longer a persistent network rules file generated in /etc/udev/rules.d And after installation OpenSuse creates the network interface eno1 (running DHCP) instead of eth0 (with static configuration) like specified, resulting in a broken network configuration. This is a major issue as it prevents dedicated server providers (which use static network configurations) from performing autoyast installations.