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

Tighten latest-kernel teardown gate

Browse Source
This commit is contained in:
Cirrus Codex
2026-05-18 16:39:31 -04:00
parent eb41631bbf
commit f4060dd324
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -85,6 +85,8 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
- Do not assume the previous IP is still valid after a reboot or network change. - Do not assume the previous IP is still valid after a reboot or network change.
- Cleanup actions that remove hosts from CMC must target only the cloned host used in the current test run. - Cleanup actions that remove hosts from CMC must target only the cloned host used in the current test run.
- Treat migration session creation failures (for either migration #1 or migration #2) as blocker-fail events. - Treat migration session creation failures (for either migration #1 or migration #2) as blocker-fail events.
- Do not power off, delete, or otherwise tear down the clone until the entire latest-kernel validation path is complete, including the second migration session, online check, and MTDI/Galaxy Migrate service/driver verification on the latest kernel.
- Do not treat the latest-kernel reboot or reinstall as the end of the test. The run is only complete after steps 55-59 have succeeded and been recorded.
## Test Procedure ## Test Procedure
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. 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.
@@ -156,12 +158,13 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
57. If migration session creation fails (including API/service errors such as 5xx), hard stop as blocker-fail. 57. If migration session creation fails (including API/service errors such as 5xx), hard stop as blocker-fail.
58. Confirm machine is online in `skidamarink` using `cirrusdata`. 58. Confirm machine is online in `skidamarink` using `cirrusdata`.
59. SSH and verify MTDI, Galaxy Migrate services/driver are up. 59. SSH and verify MTDI, Galaxy Migrate services/driver are up.
60. Success-path cleanup only: power off cloned machine. 60. Only after steps 55-59 all pass, begin success-path cleanup.
61. Success-path cleanup only: delete cloned VM and its disks from vCenter inventory. 61. Success-path cleanup only: power off cloned machine.
62. Success-path final cleanup checkpoint: 62. Success-path cleanup only: delete cloned VM and its disks from vCenter inventory.
63. Success-path final cleanup checkpoint:
- Run MCP host cleanup for `skidamarink`. - Run MCP host cleanup for `skidamarink`.
- Remove the cloned VM host entry specifically via MCP (target only this test clone host), regardless of whether CDC currently reports it as online or offline. - Remove the cloned VM host entry specifically via MCP (target only this test clone host), regardless of whether CDC currently reports it as online or offline.
63. Blocker-fail path after clone creation: 64. Blocker-fail path after clone creation:
- Stop test immediately after recording failure details. - Stop test immediately after recording failure details.
- Leave cloned VM powered on and present in inventory for manual inspection. - Leave cloned VM powered on and present in inventory for manual inspection.
- Do not run clone power-off/delete steps in blocker-fail path. - Do not run clone power-off/delete steps in blocker-fail path.