[systemd-devel] Misleading udev error messages regarding virtual interfaces

[Lennart Poettering]

On Sun, 29.06.14 17:50, Leonid Isaev (lisaev at umail.iu.edu) wrote:

> Hi,
> 
> 	I am seeing the following messages in my syslog on each boot:
> ------
> $ grep "link config " /var/log/errors.log
> 2014-06-29T09:31:39.000-04:00 hermes systemd-udevd[246]: Could not apply link config to br0
> 2014-06-29T09:31:40.000-04:00 hermes systemd-udevd[246]: Could not apply link config to veth0VRCA6
> ------
> 
> The bridge 'br0' is used for LXC containers and set up via networkd:
> ------
> $ cat /etc/systemd/network/lxc_bridge.netdev
> [NetDev]
> Name=br0
> Kind=bridge
> 
> $ cat /etc/systemd/network/lxc_bridge.network
> [Match]
> Name=br0
> 
> [Network]
> Description=LAN bridge for LXC containers
> DHCP=false
> 
> [Address]
> Address=10.137.0.1/24
> ------
> 
> The interface 'vethXXXXXX' is a container part (I guess) of the veth pair.
> 
> What is the meaning of the above errors, why are they printed, and is there a
> way to get rid of them?

I have improved the error message in git to print the actual error that
is happening. This should make it easier to figure out what is going
wrong.

Most likely you have some .link file lying around that matches the
bridge or veth device you are creating, which causes this error.

Lennart

-- 
Lennart Poettering, Red Hat