We should consider SRUing this after a new netplan release is tagged
upstream. I have verified the behavior on Jammy, Noble, Resolute and
Stonking, and they are all still exiting with 0 on error.
** Tags added: server-todo
** Changed in: netplan.io (Ubuntu Resolute)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Noble)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Stonking)
Status: Triaged => Confirmed
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
