Thank you for filing this bug and improving cloud-init. What I see in
DpkgTerminalLog.txt it looks like the failure occurs in py3compile, a
Debian/Ubuntu tool that compiles Python bytecode during package
installation (called by the #DEBHELPER# section of debian/cloud-init-
base.postinst).
This appears to be a general python 3.13 issue segfaulting exit -11 when
importing python modules and isn't necessarily a cloud-init bug but appears to
be more of a python 3.13 bug. Is this a custom version of python 3.13? If this
simple python import segfault is reproducible.
One thing to check would be to get the output of : python3.13 -c 'import
sys; print(sys.version)' to see if that also segfaults.
If reproducible, I think you may want to file a bug against python3 3.13
Things
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127114
Title:
package cloud-init-base 25.2-0ubuntu1~25.04.1 failed to
install/upgrade: installed cloud-init-base package post-installation
script subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2127114/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
