From baae32c1a8c9c74323d093e8e30b2886970d4f64 Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Tue, 12 May 2026 19:52:18 -0400 Subject: [PATCH] docs(test): add targeted MCP cleanup for clone host online-status lag --- tests/cmc-upgrade-kernel-test.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tests/cmc-upgrade-kernel-test.md b/tests/cmc-upgrade-kernel-test.md index 5bf18db..3c06673 100644 --- a/tests/cmc-upgrade-kernel-test.md +++ b/tests/cmc-upgrade-kernel-test.md @@ -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 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. +- Cleanup actions that remove hosts from CMC must target only the cloned host used in the current test run. ## Test Procedure 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. 39. Post-uninstall cleanup checkpoint: - 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. 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. @@ -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. 52. Success-path final cleanup checkpoint: - 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: - Stop test immediately after recording failure details. - Leave cloned VM powered on and present in inventory for manual inspection.