Repository navigation
ci: stop DPDK AMI cleanup from deleting TRex and Graviton AMIs - #139
Merged
Merged
Conversation
The x86 DPDK AMI build keeps the newest 3 AMIs matching name *dpdk*. Every AMI name starts with dpdk-stdlib-rust-, so the filter also matched TRex and Graviton AMIs. On 2026-10-24 run 40096224458 deregistered the live TRex AMI ami-0e4c5917a5313cbfd (and its snapshots), which broke the perf stack on PR #138. Match dpdk-stdlib-rust-dpdk-* and x86_64 only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What broke
PR #138's perf runs failed with
The image id '[ami-0e4c5917a5313cbfd]' does not exist. That was the live TRex AMI: built 2026-10-22 and still referenced by SSM/dpdk-stdlib-rust/ami/trex-latest.Why
The "keep last 3" cleanup in
build-dpdk-ami.ymlfilters onName=name,Values=*dpdk*. Every AMI we build is nameddpdk-stdlib-rust-…, so the filter also matches TRex and Graviton AMIs. The step keeps the 3 newest across all three types and deletes the rest, snapshots included.Evidence from the run logs:
ami-0e4c5917a5313cbfd(TRex, live) andami-05439add3b26fd1aa(Graviton).ami-06ab0eeb63c469ffa(TRex) andami-05bfc498515518cda(Graviton).The TRex AMI is rebuilt only once a week. The x86 and Graviton DPDK AMIs are rebuilt weekly and also on every packer change. Three of those builds in one week push the TRex AMI out of the top 3. Graviton survived only because its newest AMI always stayed in the top 3.
Fix
Filter on the exact DPDK name prefix
dpdk-stdlib-rust-dpdk-*andarchitecture=x86_64. This excludes TRex (named-trex-) and Graviton (arm64, same name pattern). The TRex and Graviton cleanup steps were already scoped correctly.Notes
developmenttriggers one x86 DPDK AMI build, because the workflow file is in its push paths. That build runs the fixed filter.🤖 Generated with Claude Code