fix(images): avoid wrong AMI selected for ubuntu jammy #3747
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.
This PR fixes the exact same issue as: #2214
but for ubuntu jammy instead.
Using the aws cli we can see Canonical have published eks images which match the old ami filter:
which causes the ami build to flip-flop between the standard Ubuntu server and the EKS optimised one (which is lacking in several tools) causing workflows to fail with unexpected errors.
The updated filter returns only the expected images: