"when we install python3.9, we point /usr/bin/python to 3.9, but not /usr/bin/python3"
cloud-init does use `python3` and not `python`, though I'm not sure that would change anything. $ head -1 /usr/bin/cloud-init #!/usr/bin/python3 Since we can launch the AMI and cloud-init works ok out of the box using the supported version of python, this appears to be an issue with how the environment is getting customized. Since we're still not entirely sure of the root cause, I'll leave the bug state as Incomplete, but unless we can get more information as to why the python3-jinja2 package isn't being seen in your cloud-init environment and that the cloud-init package is doing something wrong here, it doesn't look like there's anything to fix. -- 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, Ubuntu Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
