Update AWS Ubuntu version in prod #1384
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
As part of building the AMI's for the
3.1.46
release, which included Django upgrade work #1380, the build for theapp
AMI errored withNo matching distribution found for Django==4.2.11
on theInstall pip packages for app
task. The AMI was building usingUbuntu Server 18.04 LTS
which would only havePython 3.6.8
. This work should have been covered as part of the Python upgrade work in #1378, and was for the local dev environment in d909581, but not the deployment setup which uses an AWS Ubuntu AMI, independently set by querying for an AMI ID from the current release of a given image name. In order to bring production in line with our dev Ubuntu environment and unblock Django upgrades in production, we need to upgrade the server image name in the path to query as part of our packer deployment script.Testing Instructions
Checklist