Use CIDATA seed for EL/Amazon/SUSE guests (fixes EL8 boot/SSH)#34
Merged
Conversation
Validating the new AlmaLinux 8 / Rocky 8 (4.18) profiles surfaced the real gap: their cloud-init ignores the NoCloud-over-SMBIOS network seed and falls back to DataSourceNone, so the injected SSH key is never authorised and the guest is unreachable (infra_error) — the boot itself is fine (real 4.18 kernel reached the login prompt). seedDeliveryForProfile only special-cased the literal rhel-8-4.18 ID. Generalise it: select the CIDATA disk/ConfigDrive seed by distro family (rhel, almalinux, rocky, centos*, oracle, amazon-linux, sles, opensuse) — these cloud-init configs read a CIDATA volume but not the SMBIOS-net seed. Ubuntu/Debian keep the network seed. This also covers the amazon-linux-2 "transport unsupported" case. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
EL/Amazon/SUSE guests need the cloud-localds-built ConfigDrive ISO seed; without cloud-image-utils the runner falls back to a vvfat seed that fails to boot (0-byte serial). Add it to the host toolchain so enterprise-kernel validation works out of the box. Verified live: AlmaLinux 8 + Rocky 8 (4.18) now PASS load_attach with kernel_btf:yes once the package is present. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 21, 2026
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.
Found while validating the new AlmaLinux 8 / Rocky 8 (4.18) profiles on a KVM host.
Root cause (from the serial log)
The EL8 guest boots cleanly to the real backported
4.18.0-553…el8_10kernel and reaches the login prompt — but cloud-init logsDatasource DataSourceNone … Used fallback datasourceandno authorized SSH keys … for user almalinux. It ignores the NoCloud-over-SMBIOS network seed bpfcompat uses, so the injected key is never authorised → SSH fails →infra_error. Not an eBPF issue — a seed-delivery/transport gap.Fix
seedDeliveryForProfileonly special-cased the literalrhel-8-4.18ID. Generalised to select the CIDATA disk/ConfigDrive seed by distro family —rhel,almalinux,rocky,centos*,oracle,amazon-linux,sles,opensuse— which their cloud-init does read. Ubuntu/Debian keep the (working) SMBIOS-net seed. Likely also resolves theamazon-linux-2-4.14"transport unsupported" finding.Tests
TestSeedDeliveryForProfileextended (EL/Amazon/SUSE → CIDATA; Ubuntu/Debian → net);go test ./internal/vm/, vet, gofmt clean. Re-validating on the box to confirm a real load/attach verdict.🤖 Generated with Claude Code