[Bug 734676] New: network bonding does not work when used with systemd
https://bugzilla.novell.com/show_bug.cgi?id=734676 https://bugzilla.novell.com/show_bug.cgi?id=734676#c0 Summary: network bonding does not work when used with systemd Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: praise.tazio@tiscalinet.it QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I have network bonding between 2 gigabit ethernet NICs, via YaST2. It does not work when I boot the system selecting the default/systemd init system. Restarting network does not help. I need to modify bonding configuration, apply, modify bonding configuration back to the original, apply, and then bonding network works. If I choose to boot with SystemV I have no problem. Reproducible: Always Steps to Reproduce: 1.Configure Network Bonding. 2.Reboot with systemd 3.Check that network does not work and bond0 does not appear on ifconfig -a output. Actual Results: Networking does not work. Expected Results: Network Working! -- 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#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c1
Alex Savin
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c
Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c2
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c3
--- Comment #3 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c4
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c5
--- Comment #5 from Tazio Ceri
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c6
--- Comment #6 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c7
--- Comment #7 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c8
--- Comment #8 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c9
--- Comment #9 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c10
--- Comment #10 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c11
--- Comment #11 from Marius Tomaschewski
The fixes we've made (comment 3) seem to not solve the start problems; it looks like the exec in network-remotefs confuses systemd...
See also bug 744293. -- 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
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c13
--- Comment #13 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c14
--- Comment #14 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=734676
https://bugzilla.novell.com/show_bug.cgi?id=734676#c15
Marius Tomaschewski
participants (1)
-
bugzilla_noreply@novell.com