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

docs(test): add targeted MCP cleanup for clone host online-status lag

Browse Source
This commit is contained in:
anthony.wen
2026-05-12 19:52:18 -04:00
parent a89de319b6
commit baae32c1a8
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -62,6 +62,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
- If the clone is missing or identity is uncertain, stop and do not delete any other VM. - If the clone is missing or identity is uncertain, stop and do not delete any other VM.
- If any blocker occurs after clone creation, stop the test and leave the cloned VM powered on for manual inspection. - If any blocker occurs after clone creation, stop the test and leave the cloned VM powered on for manual inspection.
- Do not delete or power off the clone on blocker-fail outcomes. - Do not delete or power off the clone on blocker-fail outcomes.
- Cleanup actions that remove hosts from CMC must target only the cloned host used in the current test run.
## Test Procedure ## Test Procedure
1. Remove offline hosts in `skidamarink` using MCP offline-host cleanup. 1. Remove offline hosts in `skidamarink` using MCP offline-host cleanup.
@@ -108,7 +109,8 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
38. Uninstall CMC. 38. Uninstall CMC.
39. Post-uninstall cleanup checkpoint: 39. Post-uninstall cleanup checkpoint:
- Run MCP offline-host cleanup for `skidamarink`. - Run MCP offline-host cleanup for `skidamarink`.
- If the cloned VM is still marked online after uninstall, remove that cloned VM host entry specifically. - If the cloned VM is still marked online after uninstall, remove that cloned VM host entry specifically via MCP (target only this test clone host).
- Because CMC status can lag behind VM state, poll briefly for status transition; if still online, perform targeted MCP host removal for the tested clone.
40. Check available kernels. 40. Check available kernels.
41. Select latest-upgrade target kernel from the filtered candidate list (same major required; same minor preferred). 41. Select latest-upgrade target kernel from the filtered candidate list (same major required; same minor preferred).
42. Verify matching dev/header packages for the selected latest-upgrade target are available. 42. Verify matching dev/header packages for the selected latest-upgrade target are available.
@@ -123,7 +125,8 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
51. Success-path cleanup only: delete cloned VM and its disks from vCenter inventory. 51. Success-path cleanup only: delete cloned VM and its disks from vCenter inventory.
52. Success-path final cleanup checkpoint: 52. Success-path final cleanup checkpoint:
- Run MCP offline-host cleanup for `skidamarink`. - Run MCP offline-host cleanup for `skidamarink`.
- If the cloned VM is still marked online at the end of the test, remove that cloned VM host entry specifically. - If the cloned VM is still marked online at the end of the test, remove that cloned VM host entry specifically via MCP (target only this test clone host).
- Because CMC status can lag behind VM deletion/power-off, wait/poll briefly first; if still online, perform targeted MCP host removal for the tested clone.
53. Blocker-fail path after clone creation: 53. 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.