** Description changed: + [Impact] + Snapd will want to make use of the DBus support to call on netplan to apply network configuration changes live, when asked by snap applications. + + [Test case] + Run the following command: + $ dbus-send --print-reply --system --type=method_call --dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Apply + + You should expect to see a response like this: + + method return time=1567801560.502553 sender=:1.1712 -> destination=:1.1714 serial=6 reply_serial=2 + boolean true + + Which means the command was run; netplan configuration was applied. + + Check that any changes to the netplan YAML were applied to the + interfaces. + + [Regression potential] + Pay close attention to the behavior of the 'netplan apply' command, which has had to be slightly changed to behave correctly when run in the context of snaps (when the SNAP environment variable is set). Any issues there would have to be considered as potential regressions from the update. Regression potential is very low because the changes are limitted to ensuring there; that 'netplan apply' does the right thing in calling the dbus methods when they should, which will then run the command correctly. + Other changes are limited to providing the new netplan-dbus binary, which is self-contained. + + --- + Please backport the DBus feature in netplan to Ubuntu 16.04's version of netplan. netplan is used on Core 16; DBus support would be used by snapd.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842511 Title: Backport DBus support to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
