The bugfix was staged for the "devel" series, as the archive is still
frozen: https://git.launchpad.net/network-manager/log/

I'm uploading this into Mantic: https://git.launchpad.net/network-
manager/log/?h=ubuntu/mantic

** Description changed:

+ [ Impact ]
+ 
+  * A failure to query nmcli will fail the network-manager.postinst
+ maintainer script (using "set -e")
+ 
+  * This will make the package installation/upgrade fail
+ 
+  * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
+ connection.id con show "$UUID")" and skips the corresponding keyfile
+ with a warning message
+ 
+ [ Test Plan ]
+ 
+ $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
+ [connection]
+ id=UPTOWN.guests
+ uuid=491fa5c8-68ef-4140-8679-dca422f5c262
+ type=wifi
+ 
+ [wifi]
+ ssid=UPTOWN.guests
+ mode=infrastructure
+ mac-address=E0:9D:31:09:84:54
+ 
+ [ipv6]
+ method=auto
+ 
+ [ipv4]
+ method=auto
+ 
+ $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
+ [connection]
+ id=aaaUPTOWN
+ uuid=491fa5c8-68ef-0000-1111-dca422f5c262
+ type=wifi
+ 
+ [wifi]
+ ssid=aaaUPTOWN
+ mode=infrastructure
+ mac-address=E0:9D:31:09:84:54
+ 
+ [ipv6]
+ method=auto
+ 
+ [ipv4]
+ method=auto
+ 
+ $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
+ $ sudo nmcli con reload
+ $ ls -la /etc/NetworkManager/system-connections/
+ total 32
+ drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
+ drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
+ -rw------- 1 root root   199 Oct 17 17:05 UPTOWN.guests
+ -rw------- 1 root root   191 Oct 17 17:46 aaaUPTOWN
+ 
+ # Install network-manager from proposed
+ $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.0-1ubuntu2.1
+ 
+ # Verify you don't see an error like this, breaking the pkg install
+ Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
+ dpkg: error processing package network-manager (--configure):
+  installed network-manager package post-installation script subprocess 
returned error exit status 10
+ 
+ # Verify you see a migration log like this and the package installation is 
successful:
+ Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
+ SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
+ Migrating aaaUPTOWN (491fa5c8-68ef-0000-1111-dca422f5c262) to /etc/netplan
+ $ echo $?
+ 0
+ 
+ # Verify the good profile got migrated, while the bad one remains:
+ $ sudo grep -RH UPTOWN /etc/netplan/
+ /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        
"aaaUPTOWN":
+ /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:            
name: "aaaUPTOWN"
+ /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        name: 
"aaaUPTOWN"
+ $ ls -la /etc/NetworkManager/system-connections/
+ insgesamt 28
+ drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
+ drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
+ -rw------- 1 root root   199 Okt 17 17:05 UPTOWN.guests
+ 
+ 
+ [ Where problems could occur ]
+ 
+  * Think about what the upload changes in the software. Imagine the change is
+    wrong or breaks something else: how would this show up?
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
+ 
+  * This must '''never''' be "None" or "Low", or entirely an argument as to why
+    your upload is low risk.
+ 
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
+ 
+ [ Other Info ]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ === original bug description ===
+ 
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:
  
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
-  installed network-manager package post-installation script subprocess 
returned error exit status 10
+  installed network-manager package post-installation script subprocess 
returned error exit status 10
  
  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.
  
  Contents of the file were:
  
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
- 
  
  I've removed it from disk and the migration continued to completion.
  
  Then I got another failure on:
  
  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless
  
  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  Is it unhappy because of the . in the names?
  
  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
-  dpkg 1.22.0ubuntu1
-  apt  2.7.3
+  dpkg 1.22.0ubuntu1
+  apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
-  RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN    
-  running  1.44.2   connected  started  full          enabled     enabled  
enabled  missing  enabled
+  RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN
+  running  1.44.2   connected  started  full          enabled     enabled  
enabled  missing  enabled

** Description changed:

  [ Impact ]
  
-  * A failure to query nmcli will fail the network-manager.postinst
+  * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")
  
-  * This will make the package installation/upgrade fail
+  * This will make the package installation/upgrade fail
  
-  * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
+  * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message
  
  [ Test Plan ]
  
  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef-0000-1111-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw------- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw------- 1 root root   191 Oct 17 17:46 aaaUPTOWN
  
  # Install network-manager from proposed
  $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.0-1ubuntu2.1
  
  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10
  
  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef-0000-1111-dca422f5c262) to /etc/netplan
  $ echo $?
  0
  
  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:            
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw------- 1 root root   199 Okt 17 17:05 UPTOWN.guests
  
- 
  [ Where problems could occur ]
  
-  * Think about what the upload changes in the software. Imagine the change is
-    wrong or breaks something else: how would this show up?
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall risk of regression, but it's important
-    to make the effort to think about what ''could'' happen in the
-    event of a regression.
- 
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-    your upload is low risk.
- 
-  * This both shows the SRU team that the risks have been considered,
-    and provides guidance to testers in regression-testing the SRU.
+  * This is touching NetworkManager's maintainer script
+  * Breaking it could lead to a broken/unconfigured NetworkManager package
+  * This could render a machine's networking unusable
+  * It could break distribution upgrades on package install/configure failure
  
  [ Other Info ]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Linting was used to validate the maintainer script:
+    shellcheck --shell=sh debian/network-manager.postinst
  
  === original bug description ===
  
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:
  
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10
  
  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.
  
  Contents of the file were:
  
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  I've removed it from disk and the migration continued to completion.
  
  Then I got another failure on:
  
  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless
  
  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  Is it unhappy because of the . in the names?
  
  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN
   running  1.44.2   connected  started  full          enabled     enabled  
enabled  missing  enabled

** Changed in: network-manager (Ubuntu Mantic)
       Status: New => Triaged

** Changed in: network-manager (Ubuntu Mantic)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2039503

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")

   * This will make the package installation/upgrade fail

   * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message

  [ Test Plan ]

  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef-0000-1111-dca422f5c262
  type=wifi

  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw------- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw------- 1 root root   191 Oct 17 17:46 aaaUPTOWN

  # Install network-manager from proposed
  $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.0-1ubuntu2.1

  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef-0000-1111-dca422f5c262) to /etc/netplan
  $ echo $?
  0

  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:            
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef-0000-1111-dca422f5c262.yaml:        name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw------- 1 root root   199 Okt 17 17:05 UPTOWN.guests

  [ Where problems could occur ]

   * This is touching NetworkManager's maintainer script
   * Breaking it could lead to a broken/unconfigured NetworkManager package
   * This could render a machine's networking unusable
   * It could break distribution upgrades on package install/configure failure

  [ Other Info ]

   * Linting was used to validate the maintainer script:
     shellcheck --shell=sh debian/network-manager.postinst

  === original bug description ===

  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN
   running  1.44.2   connected  started  full          enabled     enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to