"We can test to see if installing python3-jinja2 moved us forward. Standby."
That's good if that works, but I'm still not sure how this situation happened. If I run `apt depends cloud-init`, I see `Depends: python3-jinja2` as one of the dependencies. That means that even if python3-jinja2 wasn't previously installed, it should get installed by apt when upgrading cloud-init, and it is already included when launching an EC2 Focal instance. The library should get written to /usr/lib/python3/dist-packages/jinja2, so even if you've installed python3.9 over the default system python, it should still be found regardless of the python version used. Do you have the system `python3` or `python` pointing directly to python3.9? If so, how did it get setup? Is there any other customization of your environment that you think could be affecting this? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
