No network devices configured if YAML error in any file

Bug #1746842 reported by Daniel Axtens on 2018-02-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nplan (Ubuntu)

Bug Description

- Start a VM with a network interface created by cloud-init (say ens3), and assume you have no physical console (e.g. cloud VM)
- Add another network interface (say ens7)
- Create another YAML file to configure ens7, but make a small error. This file need not reference ens3 at all!
- Reboot machine

- Observe the following message on boot
systemd[332]: /lib/systemd/systemd-generators/netplan failed with error code 1.

- Observe that you can no longer SSH in to the machine because the error in the new yaml file prevents all generation, so ens3 is not configured.

This is observed with the latest code on git. It renders the system entirely unusable unless there is an alternative way to get in.

 1) An error in the configuration of device X should not stop device Y from being configured!
 2) Users should be instructed to always run netplan-generate to test for bugs. (Maybe a wrapper like visudo or crontab -e would be good?)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers