https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c1 Alex Savin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexo.veto@gmail.com --- Comment #1 from Alex Savin 2011-12-13 05:40:46 UTC --- I have the same problem with Network Bridge -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c2 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #2 from Frederic Crozat 2012-01-19 15:35:43 UTC --- please test with latest 12.1 maintenance update for systemd and sysconfig -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c4 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |praise.tazio@tiscalinet.it AssignedTo|mvidner@suse.com |mt@suse.com --- Comment #4 from Martin Vidner 2012-01-31 15:58:03 CET --- If it works with sysvinit but not with systemd, then I think that yast does nothing wrong with the ifcfg files. Tazio, Alex, if it does not work with with updated sysconfig.rpm, please attach the files /etc/sysconfig/network/ifcfg-* Over to Marius for sysconfig.rpm, reassign back if yast configures it wrong. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c6 --- Comment #6 from Marius Tomaschewski 2012-02-01 09:13:33 UTC --- Going to retest with bonding... BTW: For the moment, you can use /./etc/init.d/network This trick aviods the redirection to systemd and back. Can you attach your network config please? Install the "supportutils" package, execute "supportconfig" and attach the resulting archive. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c8 --- Comment #8 from Marius Tomaschewski 2012-02-01 15:48:59 UTC --- Created an attachment (id=473817) --> (http://bugzilla.novell.com/attachment.cgi?id=473817) /etc/init.d/network -- test script -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c10 --- Comment #10 from Marius Tomaschewski 2012-02-01 15:59:52 UTC --- I've tried it in KVM only until now, but it seems bonding in the kernel (released few days ago) may be broken... The setup via ifup works AFAIS, but I didn't get any packets through the bond interface. The fixes we've made (comment 3) seem to not solve the start problems; it looks like the exec in network-remotefs confuses systemd... I've attached my work in progress -- please save and try out them: install -m755 bug-734676_network /etc/init.d/network install -m755 bug-734676_network-remotefs /etc/init.d/network-remotefs -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c12 --- Comment #12 from Marius Tomaschewski 2012-02-02 16:36:34 UTC --- Does it help when you add the LINK_READY_WAIT='15' setting to the /etc/sysconfig/network/ifcfg-bond0 file? Can you remove "quiet" and set the following boot time options? : splash=0 showopts systemd.log_level=debug systemd.log_target=kmsg systemd.sysv_console=1 systemd.show_status=1 I've applied my current set of changes to http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope... I've also improved the /etc/sysconfig/network/config: DEBUG=EXTRA (bash -vx) tracing to include all ifup args and pid... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c14 --- Comment #14 from Marius Tomaschewski 2012-02-16 14:10:58 UTC --- Any news? Please make sure you have the most recent systemd >= 37-3.151.1 from: http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12... install the sysconfig package (changelog from today, > 0.75.4-2.8) from: http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope... ------------------------------------------------------------------ Thu Feb 16 14:03:59 UTC 2012 - mt@suse.com - Test patch: 0010-network-start-fails-under-systemd.test.patch bnc#734676: network bonding does not work when used with systemd bnc#737636: network is started then stopped right away bnc#745859: network reports failure at start under systemd Set DEBUG=EXTRA, reboot and attach tar of /dev/.sysconfig/network. ------------------------------------------------------------------ Then set DEBUG=EXTRA in /etc/sysconfig/network/config, reboot and attach a tar.bz2 of /dev/.sysconfig/network when it occurs again. -- 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.