Good catch and thanks for reporting this issue! It seems to originate from this change: https://github.com/canonical/netplan/pull/334/files (core.py).
Would you mind creating a PR on GitHub to fix this, e.g. by adding a "sys.exit(1)" in each of those 3 exception cases, after the "logging.warning"? https://github.com/canonical/netplan/pulls ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2104373 Title: [Bug] Failed 'netplan set' operation doesn't return non-0 error (Netplan 1.1.1 in Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2104373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
