[Bug 829033] New: veth devices must not handled by udevd
https://bugzilla.novell.com/show_bug.cgi?id=829033 https://bugzilla.novell.com/show_bug.cgi?id=829033#c0 Summary: veth devices must not handled by udevd Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: richard@nod.at QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 /usr/lib/udev/rules.d/77-network.rules does not white list veth devices, if tools like libvirt create veth devices udevd runs ifup/down/hotplug on them and confuses libvirt. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c1
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c2
Marius Tomaschewski
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0
/usr/lib/udev/rules.d/77-network.rules does not white list veth devices, if tools like libvirt create veth devices udevd runs ifup/down/hotplug on them and confuses libvirt. ^^^^^^^^^^^^^^^^
How does it confuse libvirt / what are the problem you've observed? -- 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=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c3
--- Comment #3 from Richard Weinberger
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c4
--- Comment #4 from Richard Weinberger
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c5
Marius Tomaschewski
libvirt creates veth devies and sets them up/down.
Right.
If udevd also starts configuring them we end up in a situation where libvirt thinks that an interface is up, but is in reality down and vice versa.
No, udev does not create them -- it just handles the event when interface appears in the system (created by libvirt in this case) or is removed from the system/kernel (triggered by libvirt, cleanup call on sysconfig side). There is no ifcfg-file for the veth interfaces, so nothing is done and nothing happens. When there is one, it is there a) by intention or b) libvirt is trying to use a system configured/reserved interface name, that is a misconfiguration. (In reply to comment #4)
BTW: There is *zero* reason why udevd should handle virtual network devices...
e.g. routed vm configuration on the host side, we've used with xen. The user may want to create a ifcfg-file with STARTMODE=hotplug and ifroute-file to apply routes. As there is no issue, resolving as INVALID. -- 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=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c6
--- Comment #6 from Richard Weinberger
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c7
--- Comment #7 from Marius Tomaschewski
So, can you please explain me why udevd is calling "/sbin/ifdown veth5 -o hotplug"? On my system is no ifcfg file for veth5.
To mark it "rename done" (by udev; or rule 77 reached), track the state and _if_ there is ifcfg config, to start the interface. That there is no ifcfg-veth5 file, does not mean there is really no ifcfg config for the interface: it could be an iBFT interface and ifup reads the iBFT NICs as ifcfg config - it even ignores an existing ifcfg file - then. Further, when there is no iBFT but a ifcfg-file, it may have STARTMODE=off, disabling it even ifcfg file exists. A test -f file is not sufficient. -- 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=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c8
--- Comment #8 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c9
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=829033
https://bugzilla.novell.com/show_bug.cgi?id=829033#c10
Marius Tomaschewski
participants (1)
-
bugzilla_noreply@novell.com