Ubuntu
cloud-init package

package cloud-init 24.1.3-0ubuntu1~23.10.2 failed to install/upgrade: installed cloud-init package post-installation script subprocess was killed by signal (Broken pipe)

Bug #2067137 reported by maddatascientist on 2024-05-25

This bug report will be marked for expiration in 33 days if no further activity occurs. (find out why)

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-init (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

The desktop crashes after some time and a hard reboot is needed (going so far to unplug and re-plug).

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: cloud-init 24.1.3-0ubuntu1~23.10.2
ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri May 24 08:55:15 2024
DuplicateSignature:
package:cloud-init:24.1.3-0ubuntu1~23.10.2
Installing new version of config file /etc/profile.d/Z99-cloud-locale-test.sh ...
dpkg: error processing package cloud-init (--configure):
installed cloud-init package post-installation script subprocess was killed by signal (Broken pipe)
ErrorMessage: installed cloud-init package post-installation script subprocess was killed by signal (Broken pipe)
InstallationDate: Installed on 2023-12-25 (152 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1.1
apt 2.7.3ubuntu0.1
SourcePackage: cloud-init
Title: package cloud-init 24.1.3-0ubuntu1~23.10.2 failed to install/upgrade: installed cloud-init package post-installation script subprocess was killed by signal (Broken pipe)
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

maddatascientist (mds1234) wrote on 2024-05-25:

.var.log.ubuntu-advantage.log.txt Edit (26.7 KiB, text/plain; charset="utf-8")
AptOrdering.txt Edit (1.4 KiB, text/plain; charset="utf-8")
AutoInstallUserData.txt Edit (7.3 KiB, text/plain; charset="utf-8")
CurtinConfigCurtHooks.txt Edit (7.1 KiB, text/plain; charset="utf-8")
CurtinConfigExtract.txt Edit (7.1 KiB, text/plain; charset="utf-8")
CurtinConfigInitial.txt Edit (339 bytes, text/plain; charset="utf-8")
CurtinConfigPartitioning.txt Edit (5.2 KiB, text/plain; charset="utf-8")
CurtinLog.txt Edit (133.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (6.9 KiB, text/plain; charset="utf-8")
Df.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (257.5 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (6.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (10.2 KiB, text/plain; charset="utf-8")
InstallerCloudCfg.txt Edit (816 bytes, text/plain; charset="utf-8")
ProbeData.txt Edit (77.5 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
SubiquityServerDebug.txt Edit (394.9 KiB, text/plain; charset="utf-8")
UdiLog.txt Edit (2.6 MiB, text/plain; charset="utf-8")
cloud-init-log-warnings.txt Edit (884 bytes, text/plain; charset="utf-8")
cloud-init-output.log.txt.txt Edit (7.0 KiB, text/plain; charset="utf-8")
logs.tgz.gz Edit (274.4 KiB, application/x-gzip)
lshw.txt.txt Edit (46.6 KiB, text/plain; charset="utf-8")
user_data.txt.txt Edit (604 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2024-05-25

tags:

removed: need-duplicate-check

Revision history for this message

Brett Holman (holmanb) wrote on 2024-05-27:

> The desktop crashes after some time and a hard reboot is needed (going so far to unplug and re-plug).

This happens while trying to upgrade cloud-init I assume? Does this reproduce for you? I just tried upgraded cloud-init from 23.3.1-0ubuntu2 to 24.1.3-0ubuntu1~23.10.2 without error. The journal log included is from a different boot than the one where you had this issue. Can you please share the journal log from the boot you did on 05/24?

To do that please run:

journalctl -b -N

where N is 0 for current boot, -1 for previous, -2 for boot before previous, etc.

Please not that a signal which kills cloud-init during postinst doesn't necessarily mean that there is an issue with cloud-init.

Changed in cloud-init (Ubuntu):
status:	New → Incomplete

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntucloud-init package