Add offline repo gate to CMC kernel test

This commit is contained in:
Cirrus Codex
2026-05-19 11:43:38 -04:00
parent ce23fc48c4
commit ae72bc0c9a

View File

@@ -87,6 +87,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
- [ ] 1. Confirm the requested source host is not a SUSE/SLES machine.
- [ ] 2. Remove offline hosts in `skidamarink` using MCP offline-host cleanup.
- [ ] 3. Confirm source host is powered on for the inspection phase.
- [ ] 3a. Before listing available kernel builds, inspect source repository files and hard stop if any enabled/source repo points at `192.168.3.199`.
- [ ] 4. SSH to the source host and check available kernel versions on the source before cloning.
- [ ] 5. Build source-host kernel candidate list from all available versions after a fresh package metadata refresh. On Ubuntu, inspect the generic track first, then confirm candidate availability with alternate package listing methods if needed before deciding whether the generic track is usable.
- [ ] 6. Apply the candidate scope rule: same major OS family only, with same minor stream preferred.
@@ -155,6 +156,12 @@ The `Execution Checklist` above is the authoritative run ledger. Use the procedu
1. Confirm the requested source host is not a SUSE/SLES machine. If it is SUSE/SLES, hard stop immediately and do not power on, inspect, or clone the machine.
2. Remove offline hosts in `skidamarink` using MCP offline-host cleanup.
3. Confirm source host is powered on for the inspection phase. If it is powered off, power it on.
3a. Before listing available kernel builds, inspect the source host's package repository configuration files.
- Check the distro-appropriate repo sources, such as `/etc/yum.repos.d/*.repo`, `/etc/apt/sources.list`, `/etc/apt/sources.list.d/*`, `/etc/zypp/repos.d/*.repo`, and equivalent package-manager source files that exist on the machine.
- If any enabled/source repository contains `192.168.3.199`, treat the machine as using the local offline DVD/vault repository.
- Hard stop before kernel candidate discovery, fail the test, and do not clone the machine.
- Power off the source VM after inspection and confirm vCenter reports `poweredOff`.
- Append the FAIL result to both result files and explicitly note that the run was skipped because the source package repositories point at the local offline DVD/vault repository at `192.168.3.199`.
4. SSH to the source host and check available kernel versions on the source before cloning.
5. Build source-host kernel candidate list from all available versions (include intermediate versions, not just the latest from `check-update`).
- On package-managed distros, first force a fresh metadata refresh using the package manager's normal refresh command, then use the distro-appropriate tooling to list all available kernel candidates before selecting a target.