https://bugzilla.novell.com/show_bug.cgi?id=850065
https://bugzilla.novell.com/show_bug.cgi?id=850065#c3
Sebastian Herbszt changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FEATURE |
--- Comment #3 from Sebastian Herbszt 2014-04-17 15:07:19 UTC ---
I assume the L3 accident you mentioned corresponds to my SR dating back
to August 2011 (10714816549 created on 17 Aug 2011, reopened as 10804565953
on 28 Nov 2012 and reopened again as 10871306206 on 17 Dec 2013).
Can you please explain how silently ignoring configuration from autoyast
profile is a feature?
It is possible to change the network udev rules in yast during an interactive
installation from cd. After the reboot on the "Network Configuration" screen
use Change->Network Interfaces->Edit->Hardware->Udev rules->Change DeviceName
to change eth0 to net0.
After the installation is finished the network card is named net0 and
70-persistent-net.rules was modified to reflect this change. The network
configuration was stored in ifcfg-net0.
If "Clone This System for AutoYaSt" was selected the resulting profile
autoinst.xml contains the correct net-udev section.
If this profile is used for an unattended installation from cd the network
configuration is broken because the configuration file is called ifcfg-net0,
but the network card is named eth0 instead of the desired net0.
As you can see the autoyast driven installation behaves not the same as a
normal
(interactive) one.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
