http://bugzilla.suse.com/show_bug.cgi?id=906709 Florian Koch <f_koch@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(f_koch@gmx.de) | --- Comment #14 from Florian Koch <f_koch@gmx.de> --- (In reply to Werner Fink from comment #10)

(In reply to Florian Koch from comment #7)

Q: What are you doing with oS 13.2?

i use systemd-nspawn container to test things locally

To be more precisely for SLES 12 there can not be an update to systemd-217 or more recent version as this breaks several tools like multipathd, iscsi, lvm, and maybe some more due to the changed behaviour of udevd on devices and its (f)locking for those devices. And for oS 13.2 there will be also no update for nearly the same reasons.

I do not use SLES12, i only tested with an evaluation licence, and recognised the same problem.

Nevertheless instead of claiming about a fix you may do some own work at your self to help to get systemd-210 working with network veth and bridge working. Please hold in mind that openSUSE is a community project.

sorry i think you get me wrong , i know that OpenSUSE is an community project, and i have no problem to test things and try to figure out the fix myself. regards f0 -- You are receiving this mail because: You are on the CC list for the bug.