Beniamino Galvani ffeac35f04 ovs: ignore failures of patch interfaces ... When there are two patch ports connected, each of them must reference the other; however they can't be created in a single transaction because they are part of different bridges (so, different connections). Therefore, the first patch that gets activated will always fail with "No usable peer $x exists in 'system' datapath" until the second patch exists. In theory we could also match the error message, however this doesn't seem very robust as the message may slightly change in the future.		2020-06-10 09:58:25 +02:00
..
meson.build	license: Add license using SPDX identifiers to meson build files	2020-02-17 13:16:57 +01:00
nm-device-ovs-bridge.c	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
nm-device-ovs-bridge.h	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
nm-device-ovs-interface.c	shared: add nm_utils_invoke_on_timeout()	2020-04-24 13:58:46 +02:00
nm-device-ovs-interface.h	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
nm-device-ovs-port.c	ovs: fail port enslavement when the bridge device is not found	2020-02-24 15:00:46 +01:00
nm-device-ovs-port.h	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
nm-ovs-factory.c	ovs: ignore failures of patch interfaces	2020-06-10 09:58:25 +02:00
nm-ovsdb.c	ovs: enable trace logging not only with NM_MORE_LOGGING	2020-05-08 14:24:14 +02:00
nm-ovsdb.h	ovs/ovsdb: support changing the MTU of an ovs interface	2020-03-26 21:39:49 +01:00