From da0f83d3c8cb993cd763d7312f67998fc4306d37 Mon Sep 17 00:00:00 2001 From: Cirrus Codex Date: Fri, 15 May 2026 11:41:27 -0400 Subject: [PATCH] Document ESX165 as default clone host --- tests/cmc-upgrade-kernel-test.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/cmc-upgrade-kernel-test.md b/tests/cmc-upgrade-kernel-test.md index 5e858ec..132c9f0 100644 --- a/tests/cmc-upgrade-kernel-test.md +++ b/tests/cmc-upgrade-kernel-test.md @@ -11,6 +11,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re - Source VM hostname: `` - vCenter target/source location: `` - Required clone datastore: `AutomatedTest-UnitTesting` +- Default clone ESXi host: `CDS1-ESX165` / `192.168.1.165` unless the operator explicitly specifies otherwise - Initial clone access host/IP: `` - SSH username variable: `` - SSH password variable: `` @@ -67,6 +68,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re - After source-host kernel inspection is complete, power the source VM off and re-verify in vCenter that it is powered off 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. - Always use live vCenter guest-tools data to confirm the current clone IP before any SSH or polling attempt. - Re-check live vCenter guest-tools IP after clone power-on, after switching networking from static to DHCP, and after any reboot before attempting SSH. - Do not assume the previous IP is still valid after a reboot or network change. @@ -91,7 +93,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re 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. -14. Clone source VM using the resolved unique clone name on datastore `AutomatedTest-UnitTesting` only. +14. Clone source VM using the resolved unique clone name on datastore `AutomatedTest-UnitTesting` only, and place the clone on `CDS1-ESX165` / `192.168.1.165` by default unless the operator explicitly specifies a different ESXi host. 15. For the clone command destination name, pass only the VM name (for example `aw999-ubuntu24.04-1`), not an inventory path like `/CDSHQ-Eng/vm/...`; set folder separately if needed. 16. Detach the 2 FC PCI adapters from the cloned VM. 17. Verify in vCenter that both FC passthrough devices are no longer present on the clone.