[11:40] hi! i'm trying to run "netplan try" on a server, but i keep getting the following error "subprocess.CalledProcessError: Command '['udevadm', 'settle']' returned non-zero exit status 1.", any tips on how to debug this? thanks! [11:41] morantron: does netplan --debug try give you any more info? [11:51] just tried, not sure it's giving more relevant info -> https://gist.github.com/Morantron/bf7e01de9d273e9d5f517cd779ab5da9 [11:52] udevadm settle does indeed return 1, but i think that's what it is expected to do [12:14] We really should systematically capture stdout/stderr on our external calls... [12:18] morantron: what I'd do is just insert `import pdb; pdb.set_trace()` in /usr/share/netplan/netplan/cli/commands/apply.py just above the `subprocess.check_call(['udevadm', 'settle'])`, and when the trace point triggers, just run the command manually in another shell. That should give you more info. [13:22] thanks schopin, i'm gonna give it a try [13:29] yep, running "udevadm settle" or even "uvedadm --debug settle" does not give any extra info, it just takes 2 minutes, timesout and exits with code 1 [13:30] nothing in journactl? [13:31] oh well, i think i might have an unrelated hardware proble or something, that is messing with the udev queue [13:32] *problem [13:32] thanks for your help schopin [13:35] You're welcome. [16:41] Hey folks, qq. When configuring the routes under a tunnel, for the via param. Can I just pass the name of the device? Or leave that param blank? [16:42] I often write the static route as: `sudo ip r a 10.134.4.0/22 dev ipsec0` [16:52] Church: you mean that your subnet is reachable directly via your tunnel, without having to do a hop? Omitting the via should work. You might have to add on-link: true, thoug. [16:55] Yep, I'll give that a try then. [17:04] schopin: Hmm secondary qq, is there an example of using the key param to the tunnel type? [17:05] Church: I believe you'll find what you need there: https://netplan.io/reference/#properties-for-device-type-tunnels%3A