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

Require vCenter poweredOff confirmation before clone

Browse Source
This commit is contained in:
Cirrus Codex
2026-05-15 16:05:48 -04:00
parent be8f3764d7
commit 41a493ce00
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -69,7 +69,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.
- After source-host kernel inspection is complete, power the source VM off and re-verify in vCenter that it is powered off before cloning.
- After source-host kernel inspection is complete, issue the power-off request, then wait for vCenter to report the source VM as `poweredOff` before cloning.
- Detaching the 2 FC PCI passthrough adapters from the cloned VM is mandatory before any guest boot or guest-side change.
- Verify in vCenter that both FC passthrough devices are absent before proceeding past the clone-prep stage.
- Use `CDS1-ESX165` / `192.168.1.165` as the default ESXi host for the clone unless the operator explicitly specifies a different placement host.
@@ -95,8 +95,8 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
8. Gate check:
- If step 7 triggered a stop condition, execute no further steps.
- If no stop condition was triggered, continue with the next step.
9. After source-host inspection is complete, power the source VM off.
10. Confirm in vCenter that the source host is powered off before cloning.
9. After source-host inspection is complete, issue the power-off request and wait for vCenter to report the source host as `poweredOff`.
10. Confirm the source host is still `poweredOff` in vCenter immediately before cloning. Do not start the clone while the source VM is transitioning or pending power-off.
11. Determine base clone name: `aw999-[source-without-atvmxxx-]`.
12. Before cloning, check whether that clone name already exists in vCenter.
13. If the name exists, choose the next available suffixed name: `aw999-[source-without-atvmxxx-]-1`, then `-2`, then `-N` as needed.