ACK. IIRC there's a "nm-generated" flag inside the NM connection
profile, which we could check to avoid calling into the libnetplan
integration if exists.

So this actually affects NetworkManager's libnetplan integration patch
more than Netplan itself, IMO:

** Changed in: netplan
       Status: New => Triaged

** Changed in: netplan
   Importance: Undecided => Medium

** Changed in: netplan
   Importance: Medium => High

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.

  netplan network-manager plugin tries to save temporary connections

Status in netplan:
Status in network-manager package in Ubuntu:

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME          UUID                                  TYPE      DEVICE 
  vpntest       458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn       ens3   
  tun0          1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun       tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]: <error> [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '<dropped>' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: <warn>  [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to