http://bugzilla.suse.com/show_bug.cgi?id=1000732 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1000732 http://bugzilla.suse.com/show_bug.cgi?id=1000732#c2 rens groenewegen changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wicked-maintainer | |s@suse.de) | --- Comment #2 from rens groenewegen --- zypper dup is not yast. i know as much. however, yast is not capable of fixing the problem by itself. i had to manually adjust the stuff in /etc/syconfig/network in order to get it back on its feet again. perhaps you can find something in the logs why it could not do that. cheers, Rens -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1000732 http://bugzilla.suse.com/show_bug.cgi?id=1000732#c4 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com, | |snwint@suse.com Flags| |needinfo?(lnussel@suse.com) --- Comment #4 from Steffen Winterfeldt --- Yes, we've put us into a pretty mess here ourselves. 13.2: enp0s9 leap 42.1: eth0 leap 42.2: eth0 tumbleweed: enp0s9 13.2 & TW go for 'predictable' names, leap for kernel names. Can't the community make up their mind? The mac address is not stored, so you can't relate interface names based on that. One way I see would be to re-do what 80-net-setup-link.rules does in yast to see which names the interfaces would have had. FWIW, I'd add net.ifnames=0/1 to my boot options and be done either way. Ludwig, was it a deliberate decision to go for classical interface names in Leap or did it just happen? Do we have a plan to consolidate either way? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1000732 http://bugzilla.suse.com/show_bug.cgi?id=1000732#c6 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lnussel@suse.com) | --- Comment #6 from Ludwig Nussel --- Known problem when updating from 13.2: https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/#idm1402896... Yes, Leap aligns with SLE in that regard whereas TW follows upstream default systemd behavior. Nevertheless would be good if YaST could detect the situation if messed up and restore a working setup somehow. -- You are receiving this mail because: You are on the CC list for the bug.