Enable Amazon Linux 2 (4.14) validation — enterprise tier 14/14#36
Merged
Conversation
The hardcoded amazon-linux-2-4.14 UNSUPPORTED_TRANSPORT exclusion predated the CIDATA seed fix. With the seed now delivered as a ConfigDrive ISO, the legacy AL2 image boots and SSHes fine — verified on a KVM host: it passes load_attach on a real 4.14.26-54.32.amzn2 kernel with kernel_btf:no (the heavily-backported, no-BTF case). Drop the exclusion; add a transport test; update the reference matrix to 14/14. Co-Authored-By: Claude Opus 4.8 <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
1 participant
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.
Closes the last enterprise-kernel gap from the reference-matrix run.
What
amazon-linux-2-4.14was hardcoded asUNSUPPORTED_TRANSPORT("no reliable cloud-init+SSH bootstrap") — but that exclusion predated the CIDATA seed fix (#34). With the seed delivered as a ConfigDrive ISO, the legacy 2018 AL2 image boots and SSHes fine.Verified on a KVM host: it now passes
load_attachon a real4.14.26-54.32.amzn2kernel withkernel_btf:no— the heavily-backported, no-BTF case where kernel version is least predictive of feature support (exactly the original question that kicked this off).Changes
internal/vm/transport.go: drop the stale AL2 4.14 exclusion (it now falls through to SSH + CIDATA seed).internal/vm/qemu_test.go: positive transport test foramazon-linux-2-4.14.docs/case-study-enterprise-kernels.md: enterprise tier updated to 14/14; AL2 4.14 moved from gap → proven (no-BTF).go test ./internal/vm/, vet, gofmt clean.🤖 Generated with Claude Code