d/t/nm_netplan.py: Make sure NM connections are written to disk
This is to trigger the Netplan integration. It will only handle NM
connection profiles written to /etc/NetworkManager/system-connections
and ignore NM connection profiles, which are in memory or temporaray
(e.g. /run/NetworkManager/...).
d/t/nm_netplan.py: Add a test for OpenVPN connections (LP: 1998207)
This test reproduces the bug reported on LP#1998207
On NM 1.40, when we added a route to the tun0 interface it would just
work. On NM 1.42, the interface in taken down when we change it so the
client will not work.
Now that NM 1.42 will also create a connection for the loopback
interface, let's add the route to 'lo' instead.
d/t/nm_netplan.py: Add autopkgtests for the netplan integration
nm_netplan.py creates connections through the Python library. It adds
a lot of boilerplate when implementing tests though. Might be better to
just call nmcli.
- Add test to create, change and delete a tap device
- Add few more tests
Also add some support code to handle NetworkManager between tests.
- Delete interfaces if they still exist
It seems that sometimes after deleting a connection, an interface might
linger around for some reason.
- Add few more tests
- d/t/nm_netplan.py: improve formating
Remove spaces, empty lines, rename the test file to have a lower
priority when parsed and remove all the skip annotations.
d/t/nm.py: Fix autopkgtests when Netplan is in use
Some autopkgtests will fail with the libnetplan patch because a
temporary directory is mounted and unmounted for each test to store the
NM configuration. As all the related netplan yaml files will be kept in
/etc/netplan, all the deleted connections were being recreated.
Let the nm.py script also mount /etc/netplan as a tmpfs volume for each
test.
