chore(baselines): refresh stale kernel baselines via re-validation#90
Merged
Conversation
Re-fetched the current vendor cloud images and re-ran the matrix under KVM (validator load + attach), then updated vm/kernel-baselines.yaml from the report. Advances the last-validated kernel for 11 profiles to what the current images actually ship: almalinux-9, centos-stream-9, rocky-9, amazon-linux-2, amazon-linux-2023, ubuntu-22.04 (+lockdown, +minimal), ubuntu-24.04 (+minimal), ubuntu-25.10-minimal Amazon profiles pinned dated image builds, so their source_url is bumped to the newest builds (AL2 2.0.20260710.0, AL2023 2023.12.20260720.0); the rest track rolling image URLs. Freshness stale count drops 16 -> 11. The 11 that remain are either inherent image-vs-package lag (the cloud image ships a slightly older kernel than the newest package kernel-crawler tracks; closing that gap needs the in-guest kernel-sweep path, not a base-image swap) or profiles that cannot be refreshed by image swap: oracle-linux-9-uek7 (newer UEK ships via yum, not a new base image), rhel-8 (subscription- gated, no source_url), and ubuntu-25.10 GA (frozen release image). Signed-off-by: ErenAri <erenari27@gmail.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
Refreshes the kernel baselines the weekly freshness oracle compares against. Re-fetched the current vendor cloud images, re-ran the matrix under KVM (real validator load + attach via
simple-pass), and updatedvm/kernel-baselines.yamlfrom the report — i.e. the baselines advance because the images were actually re-validated, not because version strings were hand-edited.Result
Freshness stale count 16 → 11. 11 baselines advanced to the kernel the current image ships; 5 profiles are now fully fresh (amazon-linux-2, amazon-linux-2023, centos-stream-9, ubuntu-22.04-minimal, ubuntu-24.04-minimal).
Amazon profiles pin dated image builds, so their
source_urlis bumped to the newest builds (AL22.0.20260710.0, AL20232023.12.20260720.0); the other refreshed profiles track rolling image URLs.The 11 still flagged stale (and why they can't be closed by a base-image refresh)
Inherent image-vs-package lag (6) — refreshed, but the cloud image ships a kernel a point release behind the newest package kernel-crawler tracks. Closing this needs the in-guest kernel-sweep path (install the exact kernel in-guest), not a base-image swap:
almalinux-9,rocky-9,ubuntu-22.04(+lockdown),ubuntu-24.04,ubuntu-25.10-minimal.Not refreshable by image swap (5):
oracle-linux-9-uek7— newer UEK kernel ships via in-guestyum update; OL9U8 base image not published.rhel-8-4.18— subscription-gated, profile has nosource_url(operator-supplied image).ubuntu-18.04,ubuntu-20.04— ESM;currentcloud image still ships the prior kernel.ubuntu-25.10(GA, non-minimal) — frozen release image; newer kernel is an-updatespackage.Verification
All 13 target VMs booted under KVM and passed validator load checks; kernels recorded from live
uname -rinside each guest. With the new issue-filing freshness lane (#88), the tracking issue will auto-update to these 11 on its next run.