anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Prefer Ubuntu generic kernels before fallback tracks

Browse Source
This commit is contained in:
Cirrus Codex
2026-05-15 13:28:55 -04:00
parent 416e59a685
commit a3416542a4
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/cmc-upgrade-kernel-test.md
View File

@@ -82,7 +82,9 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
2. Confirm source host is powered on for the inspection phase. If it is powered off, power it on.
3. SSH to the source host and check available kernel versions on the source before cloning.
4. Build source-host kernel candidate list from all available versions (include intermediate versions, not just the latest from `check-update`).
- On Ubuntu, use `apt-cache madison` and/or `apt list -a` for `linux-image-generic`, `linux-headers-generic`, and `linux-image-generic-hwe-24.04` / `linux-headers-generic-hwe-24.04` after `apt update` so the candidate scan includes all available generic kernel tracks, not just the newest upgradable entry.
- On Ubuntu, prefer the generic kernel track first: use `apt-cache madison` and/or `apt list -a` for `linux-image-generic` and `linux-headers-generic` after `apt update`.
- If the generic track returns no usable upgrade candidates, pause and ask the operator whether to continue with alternate Ubuntu kernel tracks.
- When prompting for alternate Ubuntu tracks, display the other available kernel candidates, including `linux-image-generic-hwe-24.04` / `linux-headers-generic-hwe-24.04` when present, and wait for explicit operator confirmation before proceeding.
5. Candidate scope rule:
- Include only kernels in the same major OS family as the current machine (no major-version upgrades).
- Prefer candidates within the same minor stream as current OS/kernel when available.