http://bugzilla.suse.com/show_bug.cgi?id=945929 http://bugzilla.suse.com/show_bug.cgi?id=945929#c8 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #8 from Michal Filka <mfilka@suse.com> --- (In reply to Bob Rogers from comment #7)

I booted into the installer again, having configured the network as before, and ifconfig on a console shows that "ens2" is using that IP address. /etc/sysconfig/network/ifcfg-ens2 exists, with the same contents as before. This is true even before clicking "OK" on the "Beta" confirmation popup.

Sorry for delay. Last quarter of 2015 was really mad here, anyway .... to summarize what we currently know: - it seems there is a collision in persistent device naming used by installer (ens2) and old fashioned device names (eth0) used by target after reboot - according listing in comment#6 network configuration is correctly copied "from" installer to target (ifcfg-ens2 exists in /etc/sysconfig/network) So, it seems that "something" - disables using persistent device names after reboot, or - udev rules are malformed so that ens2 -> eth0 -- You are receiving this mail because: You are on the CC list for the bug.