[Bug 1817655] Re: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco)

[Steve Langasek]

A possible SRU regression has been reported against netplan.io
0.96-0ubuntu0.18.10.2 in LP: #1825206.  This version has been rolled
back to -proposed while the investigation is ongoing.

** Changed in: netplan.io (Ubuntu Cosmic)
       Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1817655

Title:
  NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu
  19.04 Disco)

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in netplan.io source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Netplan users who use the NetworkManager backend (ie. all desktop users);
  only when NetworkManager 1.15.2 is in use (disco and higher).

  [Test case]
  1) Apply any currently working configuration.
  2) Run 'netplan apply'
  3) Verify that the files generated in /run/NetworkManager/system-connections/ include a ".nmconnection" suffix.

  [Regression potential]
  None; this additional extension allows support for NetworkManager 1.15.2 and has additional effect on earlier version of NetworkManager: files are parsed despite any possible file suffix.

  ---

  NetworkManager 1.15.2 or later (as included first in Ubuntu 19.04 Disco Dingo) now requires that files in /{etc,run}/NetworkManager/system-connections end in the suffix '.nmconnection' as per the following commit:
  https://github.com/NetworkManager/NetworkManager/commit/648c256b9014198aac388097e410999c68c4b452

  NetPlan writes files as /run/NetworkManager/system-connections/{name}
  without any suffix. On Ubuntu 19.04 these files are ignored and the
  configuration is not applied.

  If you rename the files to end in '.nmconnection' then you can see the
  interface configuration loaded by NetworkManager.

  root at optane:/run/NetworkManager/system-connections# ls
   netplan-eno1   virbr0.nmconnection  'Wired connection 1.nmconnection'  'Wired connection 2.nmconnection'

  root at optane:/run/NetworkManager/system-connections# cat /etc/netplan/03-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
    version: 2
    renderer: NetworkManager
    ethernets:
      eno1:
        addresses: [10.48.134.22/25]
        gateway4: 10.48.134.1
        nameservers:
          addresses: [10.48.134.6]

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1817655/+subscriptions