[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2026-02-17 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 25.3-0ubuntu1~25.10.1

---
cloud-init (25.3-0ubuntu1~25.10.1) questing; urgency=medium

  * d/p/deprecation-version-boundary.patch: Pin deprecation version to 25.3
  * Upstream snapshot based on 25.3. (LP: #2131604).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/25.3/ChangeLog

cloud-init (25.3~2g890873f5-0ubuntu3) questing; urgency=medium

  * d/cloud-init-base.config: update migrate_debconf_settings to
set an empty cloud-init/datasources value once it migrates the value to
cloud-init-base/datasources. (LP: #2127022)
  * d/cloud-init-base.postinst: fix release upgrade affecting the set of
multi-line debconf value cloud-init/local-cloud-config used by MAAS.
(LP: #2127022)

 -- Chad Smith   Thu, 11 Dec 2025 11:36:31
-0700

** Changed in: cloud-init (Ubuntu Questing)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2026-01-05 Thread Patricia Domingues 
Ok. installed

cloud-init_25.3-0ubuntu1~25.10.1_all.deb (2.1 KiB)

and

cloud-init-base_25.3-0ubuntu1~25.10.1_all.deb (610.4 KiB) from questing-
proposed and then was successfully able to upgrade from P>Q, without the
issue mentioned.


Foreign Packages Installed 

The following unofficial packages are currently installed:

cloud-init...Installed from: unknown origin 
cloud-init-base..Installed from: unknown origin 


It is recommended to install supported versions from the Ubuntu 
archive, and try the upgrade again. 

Do you want to continue the upgrade anyways?

Continue [yN] y
...
System upgrade is complete.
 
Restart required 

To finish the upgrade, a restart is required. 
If you select 'y' the system will be restarted. 

Continue [yN] y
...
ubuntu@P10rain-LPAR10:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 25.10
Release:25.10
Codename:   questing


** Tags removed: verification-needed verification-needed-questing
** Tags added: verification-done verification-done-questing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-17 Thread Nick Rosbrook 
Hello Patricia, or anyone else affected,

Accepted cloud-init into questing-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/25.3-0ubuntu1~25.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-questing
** Tags added: verification-needed verification-needed-questing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-12 Thread Chad Smith 
Note this bugfix SRU blocks a more general cloud-init 25.3 SRU LP:
#2131604  which will follow immediately after this bugfix only SRU
publishes to  questing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-10 Thread Chad Smith 
Questing Validation complete with success for both scenario 1 (with no
MAAS debconf settings) and scenario 2 (with MAAS debconf setting)

Tracking SUCCESS comments on commandline for the above test procedure.


csmith@midtown:~/src/cloud-init$ lxc launch ubuntu-daily:questing test-2127022
Launching test-2127022
csmith@midtown:~/src/cloud-init$  lxc file push setup_proposed.sh test-2127022/
csmith@midtown:~/src/cloud-init$ lxc exec test-2127022 bash
root@test-2127022:~# debconf-show cloud-init > debconf.cloud-init.orig
debconf-show cloud-init-base >> debconf.cloud-init.orig
root@test-2127022:~# cat debconf.cloud-init.orig 
* cloud-init/datasources: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, None
  cloud-init-base/datasources: NoCloud, ConfigDrive, OpenNebula, DigitalOcean, 
Azure, AltCloud, VMware, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, 
Bigstep, Scaleway, AliYun, Ec2, CloudStack, Hetzner, IBMCloud, Oracle, 
Exoscale, RbxCloud, UpCloud, Vultr, LXD, NWCS, Akamai, WSL, CloudCIX, None
root@test-2127022:~#  cp -r /etc/cloud/cloud.cfg.d .
root@test-2127022:~# bash /setup_proposed.sh
Types: deb
URIs: http://archive.ubuntu.com/ubuntu
Suites: questing-proposed
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
Get:1 http://security.ubuntu.com/ubuntu questing-security InRelease [136 kB]
Get:2 http://archive.ubuntu.com/ubuntu questing-proposed InRelease [275 kB]
Get:3 http://security.ubuntu.com/ubuntu questing-security/main amd64 Packages 
[106 kB]
Get:4 http://security.ubuntu.com/ubuntu questing-security/main Translation-en 
[29.2 kB]
Get:5 http://security.ubuntu.com/ubuntu questing-security/main amd64 Components 
[208 B]
Get:6 http://security.ubuntu.com/ubuntu questing-security/main amd64 c-n-f 
Metadata [3132 B]
Get:7 http://security.ubuntu.com/ubuntu questing-security/universe amd64 
Packages [74.0 kB]
Get:8 http://security.ubuntu.com/ubuntu questing-security/universe 
Translation-en [22.9 kB]
Get:9 http://security.ubuntu.com/ubuntu questing-security/universe amd64 
Components [6764 B]
Get:10 http://security.ubuntu.com/ubuntu questing-security/universe amd64 c-n-f 
Metadata [2344 B]
Get:11 http://security.ubuntu.com/ubuntu questing-security/restricted amd64 
Packages [82.5 kB]
Get:12 http://security.ubuntu.com/ubuntu questing-security/restricted 
Translation-en [18.4 kB]
Get:13 http://security.ubuntu.com/ubuntu questing-security/restricted amd64 
Components [208 B]
Get:14 http://security.ubuntu.com/ubuntu questing-security/multiverse amd64 
Packages [1676 B]
Get:15 http://security.ubuntu.com/ubuntu questing-security/multiverse 
Translation-en [616 B]
Get:16 http://security.ubuntu.com/ubuntu questing-security/multiverse amd64 
Components [212 B]
Get:17 http://security.ubuntu.com/ubuntu questing-security/multiverse amd64 
c-n-f Metadata [224 B]
Hit:18 http://archive.ubuntu.com/ubuntu questing InRelease
Get:19 http://archive.ubuntu.com/ubuntu questing-updates InRelease [136 kB]
Get:20 http://archive.ubuntu.com/ubuntu questing-backports InRelease [133 kB]
Get:21 http://archive.ubuntu.com/ubuntu questing-proposed/main amd64 Packages 
[127 kB]
Get:22 http://archive.ubuntu.com/ubuntu questing-proposed/main Translation-en 
[30.7 kB]
Get:23 http://archive.ubuntu.com/ubuntu questing-proposed/main amd64 Components 
[25.0 kB]
Get:24 http://archive.ubuntu.com/ubuntu questing-proposed/main amd64 c-n-f 
Metadata [2272 B]
Get:25 http://archive.ubuntu.com/ubuntu questing-proposed/universe amd64 
Packages [68.7 kB]
Get:26 http://archive.ubuntu.com/ubuntu questing-proposed/universe 
Translation-en [24.8 kB]
Get:27 http://archive.ubuntu.com/ubuntu questing-proposed/universe amd64 
Components [16.5 kB]
Get:28 http://archive.ubuntu.com/ubuntu questing-proposed/universe amd64 c-n-f 
Metadata [2484 B]
Get:29 http://archive.ubuntu.com/ubuntu questing-proposed/restricted amd64 
Packages [65.7 kB]
Get:30 http://archive.ubuntu.com/ubuntu questing-proposed/restricted 
Translation-en [13.0 kB]
Get:31 http://archive.ubuntu.com/ubuntu questing-proposed/restricted amd64 
Components [216 B]
Get:32 http://archive.ubuntu.com/ubuntu questing-proposed/restricted amd64 
c-n-f Metadata [336 B]
Get:33 http://archive.ubuntu.com/ubuntu questing-proposed/multiverse amd64 
Packages [1672 B]
Get:34 http://archive.ubuntu.com/ubuntu questing-proposed/multiverse 
Translation-en [788 B]
Get:35 http://archive.ubuntu.com/ubuntu questing-proposed/multiverse amd64 
Components [216 B]
Get:36 http://archive.ubuntu.com/ubuntu questing-proposed/multiverse amd64 
c-n-f Metadata [224 B]
Get:37 http://archive.ubuntu.com/ubuntu questing/universe amd64 Packages [15.6 
MB]
Get:38 http://archive.ubuntu.com/ubuntu questing/universe Translation-en [6283 
kB]
Get:39 http://archive.ubuntu.com/ubuntu questing/universe amd64 Components 
[4600 kB]
Get:40 http://archive.ubuntu.com/ubuntu questing/universe amd64 c-n-f Metadata 
[310 kB]
Get:41 http://archive.ubuntu.com/ubuntu questing/multiverse amd64 Packages [274 
k

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-10 Thread Chad Smith 
** Description changed:

  [ Impact ]
  
   * MAAS systems make use of a number of debconf settings which are read
  by cloud-init-base.postinst in order to create configuration files in
  /etc/cloud/cloud.cfg.d to instruct cloud-init how to obtain
  configuration information from the MAAS provisioning server. In the
  presence of multi-line settings, cloud-init-base.postinst fails to
  complete package upgrade resulting in invalid apt configuration and
  manual intervention of APT unattended upgrades on MAAS-provisioned
  machines and VMs. This postinst failure breaks automatic upgrades on
  MAAS systems.
  
- 
  [ Test Plan ]
  
   * Assert upgrade path to -proposed doesn't create unexpected
  /etc/cloud/cloud.cfg.d files due to cloud-init-base.postinst processing
  of debconf values on standard cloud images in non-MAAS environment
  
  cat > setup_proposed.sh  debconf.cloud-init.orig
  debconf-show cloud-init-base >> debconf.cloud-init.orig
  
  # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
  cp -r /etc/cloud/cloud.cfg.d .
  
  bash /setup_proposed.sh
  # Upgrade and ensure exit 0 and no errors
  echo $?
  
  debconf-show cloud-init > debconf.cloud-init.new
  debconf-show cloud-init-base >> debconf.cloud-init.new
  
  # expect no new config files created by postinst
  diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
  
   * Assert multi-line debconf settings used by MAAS are properly
  processed and written to /etc/cloud/cloud.cfg.d by cloud-init-
  base.postinst
  
  # provide multi-line value matching MAAS provisioning config debconf settings
  cat > selections < debconf.cloud-init.orig
  debconf-show cloud-init-base >> debconf.cloud-init.orig
  
  # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
  cp -r /etc/cloud/cloud.cfg.d .
  
  bash /setup_proposed.sh
  # Upgrade and ensure exit 0 and no errors
  echo $?
  
  debconf-show cloud-init > debconf.cloud-init.new
  debconf-show cloud-init-base >> debconf.cloud-init.new
  
  # expect 1 new config file created by postinst 90_dpkg_cloud_init_local.cfg
  diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
  
  [ Where problems could occur ]
  
   * Problems processing cloud-init or cloud-init-base debconf settings
  can show up across package upgrade path due to cloud-init-base.postinst
  use of db_get and db_set tooling to read and write debconfig
  configuration settings. Errors during  package upgrade can result in
  non-zero exit codes from cloud-init-base.postinst which can result in
  errors affecting automatic upgrades which would force manual
  intervention to resolve or ignore such post install errors as seen in
  the original bug
  
   * Specific to MAAS debconf value processing, invalid handling of db_get 
results could result regressions by creating invalid cloud-config artifacts in 
/etc/cloud/cloud.cfg.d which would generate cloud-init schema warnings at boot 
resulting from exit 2 from such tools as `cloud-init status`.
  This type of regression has been seen in Resolute series 
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2131809
  
  [ Other Info ]
  
  = Original description =
  
  Trying to upgrade a Power10 node from Ubuntu 25.04 Plucky to 25.10
  Questing (do-release-upgrade -d) :
  
  ```
  Found initrd image: /boot/initrd.img-6.14.0-33-generic
  Warning: os-prober will not be executed to detect other bootable partitions.
  Systems on them will not be added to the GRUB boot configuration.
  Check GRUB_DISABLE_OS_PROBER documentation entry.
  Adding boot menu entry for UEFI Firmware Settings ...
  done
  Processing triggers for ca-certificates (20250419) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for initramfs-tools (0.150ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-6.17.0-5-generic
  Errors were encountered while processing:
   cloud-init-base
   cloud-init
  needrestart is being skipped since dpkg has failed
  packages have been installed but needrestart is suspended
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
  
  *** Send problem report to the developers?
  
  After the problem report has been sent, please fill out the form in the
  automatically opened

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-10 Thread Nick Rosbrook 
Hello Patricia, or anyone else affected,

Accepted cloud-init into questing-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/25.3~2g890873f5-0ubuntu3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cloud-init (Ubuntu Questing)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-questing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-10 Thread Nick Rosbrook 
** Also affects: cloud-init (Ubuntu Questing)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-08 Thread Chad Smith 
** Description changed:

  [ Impact ]
  
-  * MAAS systems make use of a number of debcon
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+  * MAAS systems make use of a number of debconf settings which are read
+ by cloud-init-base.postinst in order to create configuration files in
+ /etc/cloud/cloud.cfg.d to instruct cloud-init how to obtain
+ configuration information from the MAAS provisioning server. In the
+ presence of multi-line settings, cloud-init-base.postinst fails to
+ complete package upgrade resulting in invalid apt configuration and
+ manual intervention of APT unattended upgrades on MAAS-provisioned
+ machines and VMs. This postinst failure breaks automatic upgrades on
+ MAAS systems.
+ 
  
  [ Test Plan ]
  
-  * Assert upgrade path to -proposed doesn't create unexpected
+  * Assert upgrade path to -proposed doesn't create unexpected
  /etc/cloud/cloud.cfg.d files due to cloud-init-base.postinst processing
  of debconf values on standard cloud images in non-MAAS environment
- 
  
  cat > setup_proposed.sh  debconf.cloud-init.orig
  debconf-show cloud-init-base >> debconf.cloud-init.orig
  
  # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
  cp -r /etc/cloud/cloud.cfg.d .
  
  bash /setup_proposed.sh
  # Upgrade and ensure exit 0 and no errors
  echo $?
  
  debconf-show cloud-init > debconf.cloud-init.new
  debconf-show cloud-init-base >> debconf.cloud-init.new
  
  # expect no new config files created by postinst
  diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
  
- 
-  * Assert multi-line debconf settings used by MAAS are properly processed and 
written to /etc/cloud/cloud.cfg.d by cloud-init-base.postinst
+  * Assert multi-line debconf settings used by MAAS are properly
+ processed and written to /etc/cloud/cloud.cfg.d by cloud-init-
+ base.postinst
  
  # provide multi-line value matching MAAS provisioning config debconf settings
  cat > selections < debconf.cloud-init.orig
  debconf-show cloud-init-base >> debconf.cloud-init.orig
  
  # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
  cp -r /etc/cloud/cloud.cfg.d .
  
  bash /setup_proposed.sh
  # Upgrade and ensure exit 0 and no errors
  echo $?
  
  debconf-show cloud-init > debconf.cloud-init.new
  debconf-show cloud-init-base >> debconf.cloud-init.new
  
  # expect 1 new config file created by postinst 90_dpkg_cloud_init_local.cfg
  diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
  
- 
  [ Where problems could occur ]
  
-  * Problems processing cloud-init or cloud-init-base debconf settings can 
show up across package upgrade path due to cloud-init-base.postinst use of 
db_get and db_set tooling to read and write debconfig configuration settings. 
Errors during  package upgrade can result in non-zero exit codes from 
cloud-init-base.postinst which can result in errors affecting automatic 
upgrades which would force manual intervention to resolve or ignore such post 
install errors as seen in the original bug
-  
-  * Specific to MAAS debconf value processing, invalid handling of db_get 
results could result regressions by creating invalid cloud-config artifacts in 
/etc/cloud/cloud.cfg.d which would generate cloud-init schema warnings at boot 
resulting from exit 2 from such tools as `cloud-init status`. 
+  * Problems processing cloud-init or cloud-init-base debconf settings
+ can show up across package upgrade path due to cloud-init-base.postinst
+ use of db_get and db_set tooling to read and write debconfig
+ configuration settings. Errors during  package upgrade can result in
+ non-zero exit codes from cloud-init-base.postinst which can result in
+ errors affecting automatic upgrades which would force manual
+ intervention to resolve or ignore such post install errors as seen in
+ the original bug
+ 
+  * Specific to MAAS debconf value processing, invalid handling of db_get 
results could result regressions by creating invalid cloud-config artifacts in 
/etc/cloud/cloud.cfg.d which would generate cloud-init schema warnings at boot 
resulting from exit 2 from such tools as `cloud-init status`.
  This type of regression has been seen in Resolute series 
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2131809
- 
  
  [ Other Info ]
  
- 
  = Original description =
- 
  
  Trying to upgrade a Power10 node from Ubuntu 25.04 Plucky to 25.10
  Questing (do-release-upgrade -d) :
  
  ```
  Found initrd image: /boot/initrd.img-6.14.0-33-generic
  Warning: os-prober will not be executed to detect other bootable parti

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-08 Thread Chad Smith 
Thank you tjaalton. I have updated to SRU template to represent upgrade
path with and without MAAS-specific debconf settings to establish
correct behavior in both common case versus MAAS-specific case.


** Description changed:

+ [ Impact ]
+ 
+  * MAAS systems make use of a number of debcon
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [ Test Plan ]
+ 
+  * Assert upgrade path to -proposed doesn't create unexpected
+ /etc/cloud/cloud.cfg.d files due to cloud-init-base.postinst processing
+ of debconf values on standard cloud images in non-MAAS environment
+ 
+ 
+ cat > setup_proposed.sh  debconf.cloud-init.orig
+ debconf-show cloud-init-base >> debconf.cloud-init.orig
+ 
+ # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
+ cp -r /etc/cloud/cloud.cfg.d .
+ 
+ bash /setup_proposed.sh
+ # Upgrade and ensure exit 0 and no errors
+ echo $?
+ 
+ debconf-show cloud-init > debconf.cloud-init.new
+ debconf-show cloud-init-base >> debconf.cloud-init.new
+ 
+ # expect no new config files created by postinst
+ diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
+ 
+ 
+  * Assert multi-line debconf settings used by MAAS are properly processed and 
written to /etc/cloud/cloud.cfg.d by cloud-init-base.postinst
+ 
+ # provide multi-line value matching MAAS provisioning config debconf settings
+ cat > selections < debconf.cloud-init.orig
+ debconf-show cloud-init-base >> debconf.cloud-init.orig
+ 
+ # Copy existing /etc/cloud/cloud.cfg.d to ensure no new files on upgrade
+ cp -r /etc/cloud/cloud.cfg.d .
+ 
+ bash /setup_proposed.sh
+ # Upgrade and ensure exit 0 and no errors
+ echo $?
+ 
+ debconf-show cloud-init > debconf.cloud-init.new
+ debconf-show cloud-init-base >> debconf.cloud-init.new
+ 
+ # expect 1 new config file created by postinst 90_dpkg_cloud_init_local.cfg
+ diff -urN cloud.cfg.d /etc/cloud/cloud.cfg.d/
+ 
+ 
+ [ Where problems could occur ]
+ 
+  * Problems processing cloud-init or cloud-init-base debconf settings can 
show up across package upgrade path due to cloud-init-base.postinst use of 
db_get and db_set tooling to read and write debconfig configuration settings. 
Errors during  package upgrade can result in non-zero exit codes from 
cloud-init-base.postinst which can result in errors affecting automatic 
upgrades which would force manual intervention to resolve or ignore such post 
install errors as seen in the original bug
+  
+  * Specific to MAAS debconf value processing, invalid handling of db_get 
results could result regressions by creating invalid cloud-config artifacts in 
/etc/cloud/cloud.cfg.d which would generate cloud-init schema warnings at boot 
resulting from exit 2 from such tools as `cloud-init status`. 
+ This type of regression has been seen in Resolute series 
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2131809
+ 
+ 
+ [ Other Info ]
+ 
+ 
+ = Original description =
+ 
+ 
  Trying to upgrade a Power10 node from Ubuntu 25.04 Plucky to 25.10
  Questing (do-release-upgrade -d) :
  
  ```
  Found initrd image: /boot/initrd.img-6.14.0-33-generic
  Warning: os-prober will not be executed to detect other bootable partitions.
  Systems on them will not be added to the GRUB boot configuration.
  Check GRUB_DISABLE_OS_PROBER documentation entry.
  Adding boot menu entry for UEFI Firmware Settings ...
  done
  Processing triggers for ca-certificates (20250419) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for initramfs-tools (0.150ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-6.17.0-5-generic
  Errors were encountered while processing:
-  cloud-init-base
-  cloud-init
+  cloud-init-base
+  cloud-init
  needrestart is being skipped since dpkg has failed
  packages have been installed but needrestart is suspended
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
- 
  
  *** Send problem report to the developers?
  
  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.
  
  What would you like to do? Your options are:
-   S: Send report (345.0 KB)
-   V: View report
-   K: Keep report file for sending later or copying to somewhere else
-   I: Cancel and ignore future crashes of this program version
-   C: Cancel
- Please choose (S/V/K/I/C): 
- 
+   S: Send report (345.0 KB)
+   V: View report
+   K: Keep report file for sending later or copying to somewhere else
+   

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-12-05 Thread Timo Aaltonen 
ping? it should not have been sponsored without the required SRU info

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-11-29 Thread Timo Aaltonen 
please add the required sru information in the description

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-31 Thread Mitchell Augustin 
> In practice, this is only set in certain MAAS environments MAAS server
< 3.5 and upgrades from cloud-init in Plucky to Questing

FYI, I think I just experienced this as well 2x on machines deployed in
our MAAS running v3.5.8
(https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2130379)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-28 Thread Patricia Domingues 
** Changed in: ubuntu-power-systems
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-28 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 25.4~1gcb12e00e-0ubuntu1

---
cloud-init (25.4~1gcb12e00e-0ubuntu1) resolute; urgency=medium

  * d/cloud-init-base.config: update migrate_debconf_settings to
set an empty cloud-init/datasources value once it migrates the value to
cloud-init-base/datasources. (LP: #2127022)
  * d/cloud-init-base.postinst: fix release upgrade affecting the set of
multi-line debconf value cloud-init/local-cloud-config used by MAAS.
(LP: #2127022)

 -- Chad Smith   Fri, 10 Oct 2025 16:58:05
-0600

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-18 Thread Chad Smith 
Thank you @patriciasd for the bug.

I can confirm failure path reproducer in cloud-init-base.postinst when
upgrading systems which have set a debconfig multi-line value for cloud-
init/local-cloud-config.

In practice, this is only set in certain MAAS environments MAAS server <
3.5 and upgrades from cloud-init in Plucky to Questing.


I'll have a PPA up to allow testing prior to SRU to questing.

We also will add separate integration-test coverage in cloud-init's
existing testing to preseed known MAAS debconf settings in order to
better exercise this postinst path in the future.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-18 Thread Chad Smith 
** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Critical

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Chad Smith (chad.smith)

** Changed in: cloud-init (Ubuntu)
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-17 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2127022] Re: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

2025-10-17 Thread Dan Bungert 
** Summary changed:

- upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 
failed to install/upgrade
+ upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 
failed to install/upgrade on MAAS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127022

Title:
  upgrade from Plucky to Questing cloud-init-base
  25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs