Backport re-start service fix to xenial
Bug #1855876 reported by
Alfonso Sanchez-Beato
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netplan.io (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
| nplan (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
The backport to support netplan as a DBus service (LP: #1842511) is not complete without making sure that the network daemons are re-started as expected. The fix is included in Bionic, but not in Xenial. The upstream commit is https:/
[Test case]
Set NM as default renderer in a server installation with:
network:
renderer: NetworkManager
Check the PIDs for NM and systemd-networkd. Run
netplan apply
And check that both processes have re-started.
[Regression potential]
The change is well confined and should not be difficult to port it back. Attention to the processes re-starting also in the previous use cases should be given.
| no longer affects: | netplan |
Revision history for this message
| Lukas Märdian (slyon) wrote | #1 |
| Changed in nplan (Ubuntu): | |
| status: | New → Won't Fix |
| Changed in netplan.io (Ubuntu): | |
| status: | New → Won't Fix |
To post a comment you must log in.
Marking as WONTFIX as Xenial is EOL