I think that make sense. I think we don't actual need to make the
python3.9 the default for what we are trying to do originally. That
said, even when we didn't make python3.9 the default, it was still
breaking. :confused:
At any event, I'll going to revert the change at some point and get back
to
Public bug reported:
Summary -
Ubuntu Release:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.6 LTS
Release:20.04
Codename: focal
Package Version: 24.1.3-0ubuntu1~20.04.1
Expected behavior: cloud-init should (re)start up successfully after an
update.
Actual behavio
Note: We are running off the official Ubuntu provided image on AWS. Here
is the URL and AMI
https://console.aws.amazon.com/ec2/home?region=us-
east-1#launchAmi=ami-0e3a6d8ff4c8fe246
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
To answer:
> How are you running Python 3.9 in Focal?
We installed Python 3.9 from Focal's upstream. No third party.
> Are you using the cloud-init package provided by Apt?
Yes, because we started to see the issue after the OS update. We switch
AMIs, thinking that the OS update was problematic
As it turns out, python3-jinja2 is installed. This is output after the
upgrade to cloud-init
root@IP-INSTANCE-REDACT:~# systemctl status cloud-init
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor
To answer your question, we usually installed python3.9 on Ubuntu 20.04
like so:
DEBIAN_FRONTEND=noninteractive apt-get -y install -m -f python3.9
python3.9-distutils
update-alternatives --install /usr/bin/python python /usr/bin/python3.9 10
curl https://bootstrap.pypa.io/get-pip.py -
TLDR; when we install python3.9, we point /usr/bin/python to 3.9, but
not /usr/bin/python3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066066
Title:
cloud-init startup failure with Python 3.9.5,
What is considered a supported version of Python? Would Python3.9 from
upstream be considered a supported version?
That said, I re-tested today and it appears that the issue no longer
exists. Interestingly enough, there was a new image that was released
yesterday - ami-03e9149278a6f457c (Date 2024
