No; by now this is working exactly as expected; netplan should return 0
as long as there is no actual syntax error in the netplan config; for
now everything else is left to the backends.
** Changed in: nplan (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: netplan
Status:
I'm seeing the same thing in LP:1835275 except netplan doesn't output
any errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701434
Title:
netplan apply always exits with status 0
To manage
It looks like at least some of this changed between Bionic and Cosmic -
here with a netplan 0.39:
root@netplan:~# netplan apply
Error in network definition /etc/netplan/50-cloud-init.yaml line 5 column 0:
unknown key xxnetwork
root@netplan:~# echo $?
78
--
You received this bug notification
I'm marking this as confirmed as the behaviour has come up in LP:
#1735318.
** Changed in: netplan
Status: Incomplete => Confirmed
** Changed in: nplan (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: id-5966b86bf4d6cb1ad360527b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701434
Title:
netplan apply always exits with status 0
To manage notifications about this bug go to:
Was there any config provided when you did this? Seems like there are
also all the service stop/start commands that should get attempted and
fail (and these do throw exceptions). I don't think failing to unbind
because of a missing file, for example, is critical enough to warrant to
completing the
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Importance: Undecided => High
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => Triaged
** Changed in: nplan (Ubuntu)
Importance:
