Thomas Haller 5d09a75fe1 library: wait for connection to disappear from libnm cache during delete ... We delete the connection asynchrnonously using libnm. Even after the asynchronous request completes, the connection may still in the cache. That is a bit odd, but maybe not a bug in libnm. Because it can happen that the connection was active, so it takes time to bring it down. Maybe the asynchronous request should not complete in libnm before the connection is truly gone. But note that deactivating a connection can take arbitrary long, so it's not clear that his would be the best behavior. Anyway, work around it by waiting. The effect of this bug is if you have "state: absent" followed by "state:up", then the intermediate "present" state will be skipped. That is, because it appears that the connection still exists, although it's about to be deleted. The subsequent "up" will then fail as the connection is gone in the meantime. https://github.com/linux-system-roles/network/issues/7 https://bugzilla.redhat.com/show_bug.cgi?id=1478910		2017-08-24 18:19:06 +02:00
..
network_connections.py	library: wait for connection to disappear from libnm cache during delete	2017-08-24 18:19:06 +02:00
test_network_connections.py	add support for "infiniband" type	2017-08-02 20:50:37 +02:00