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

Record Ubuntu 24.04 pass and tighten source power-off gate

Browse Source
This commit is contained in:
Cirrus Codex
2026-05-15 15:59:27 -04:00
parent be8f3764d7
commit b0666954ff
3 changed files with 116 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 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.
- 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. - 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. - 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. - 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: 8. Gate check:
- If step 7 triggered a stop condition, execute no further steps. - If step 7 triggered a stop condition, execute no further steps.
- If no stop condition was triggered, continue with the next step. - If no stop condition was triggered, continue with the next step.
9. After source-host inspection is complete, power the source VM off. 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 in vCenter that the source host is powered off before cloning. 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-]`. 11. Determine base clone name: `aw999-[source-without-atvmxxx-]`.
12. Before cloning, check whether that clone name already exists in vCenter. 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. 13. If the name exists, choose the next available suffixed name: `aw999-[source-without-atvmxxx-]-1`, then `-2`, then `-N` as needed.

97
tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-results.md
View File

@@ -50,6 +50,103 @@ Test file: `cmc-upgrade-kernel-test.md`
--- ---
## Host Metadata
- Test date/time (UTC): 2026-05-15 17:39 UTC
- Test duration: 23m
- Operator: codex
- Source VM: atvm121-ubuntu24.04
- Cloned VM name: aw999-ubuntu24.04-1
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.111
## Kernel / OS Tracking
- Start OS version: Ubuntu 24.04 LTS
- Start kernel version: 6.8.0-31-generic
- Kernel list before first upgrade (full candidate list, filtered by scope rule): linux-image-6.8.0-117-generic 6.8.0-117.117 available; linux-image-6.8.0-111-generic 6.8.0-111.111 available; linux-image-6.8.0-31-generic 6.8.0-31.31 available
- Kernel selected for step-up upgrade: 6.8.0-111-generic
- Kernel after step-up reboot: 6.8.0-111-generic
- Installed dev/header package versions after step-up: linux-headers-6.8.0-111 6.8.0-111.111; linux-headers-6.8.0-111-generic 6.8.0-111.111; linux-image-6.8.0-111-generic 6.8.0-111.111; linux-modules-6.8.0-111-generic 6.8.0-111.111
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): linux-image-6.8.0-117-generic 6.8.0-117.117 available; linux-image-6.8.0-111-generic 6.8.0-111.111 available; linux-image-6.8.0-31-generic 6.8.0-31.31 available
- Kernel selected for latest upgrade: linux-image-6.8.0-117-generic / linux-headers-6.8.0-117-generic
- Kernel after latest reboot: 6.8.0-117-generic
- Installed dev/header package versions after latest upgrade: linux-headers-6.8.0-117 6.8.0-117.117; linux-headers-6.8.0-117-generic 6.8.0-117.117; linux-image-6.8.0-117-generic 6.8.0-117.117; linux-modules-6.8.0-117-generic 6.8.0-117.117
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: PASS - clone `aw999-ubuntu24.04-1` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-ubuntu24-04-1`; static `192.168.3.191` was removed and the clone came back on DHCP `192.168.0.111`
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `7d0d76a9-dfc1-40b4-8df9-0da26fd223e5` reached TRACKING
- Step-up kernel upgrade: PASS - installed `6.8.0-111-generic`
- Step-up dev/header package match check: PASS - matching `linux-headers-6.8.0-111-generic` and `linux-modules-6.8.0-111-generic` were installed
- Online in skidamarink after step-up: PASS - host `aw999-ubuntu24-04-1` was visible and connected in CDC
- MTDI/Galaxy Migrate service+driver health after step-up: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi-driver` were active
- Write data + tracking status: PASS - wrote `aw.dat` to `/mnt/disk1` and the session returned to TRACKING after trigger-sync
- CMC uninstall: PASS - `galaxy-migrate` and `mtdi-daemon` were removed cleanly
- Latest kernel upgrade: PASS - installed `6.8.0-117-generic`
- Latest dev/header package match check: PASS - matching `linux-headers-6.8.0-117-generic` and `linux-modules-6.8.0-117-generic` were installed
- CMC reinstall #2: PASS - host re-registered in CDC on the latest kernel
- Local migration #2 (10GB -> 11GB) initial sync: PASS - session `2956265f-961a-4df0-ab08-1a862b230434` reached TRACKING
- Online in skidamarink after latest upgrade: PASS - host `aw999-ubuntu24-04-1` was connected in CDC after reinstall
- MTDI/Galaxy Migrate service+driver health after latest upgrade: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi-driver` were active
- Clone power off and deletion (success path only): PASS - VM was powered off, destroyed in vCenter, and the offline CDC host entry was removed on cleanup
## Final Outcome
- Overall result: PASS
- Blocking issue summary: none
- Follow-up actions: none
---
## Host Metadata
- Test date/time (UTC): 2026-05-15 17:12 UTC
- Test duration: not completed
- Operator: codex
- Source VM: atvm121-ubuntu24.04
- Cloned VM name: not created
- Clone origin (vCenter path/folder/cluster): not reached
- Final DHCP IP of clone: not reached
## Kernel / OS Tracking
- Start OS version: Ubuntu 24.04 LTS
- Start kernel version: 6.8.0-31-generic
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 6.8.0-111.111
- Kernel selected for step-up upgrade: not reached
- Matching dev/header packages for step-up target (availability check): not reached
- Kernel after step-up reboot: not reached
- Installed dev/header package versions after step-up: not reached
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): not reached
- Kernel selected for latest upgrade: not reached
- Matching dev/header packages for latest target (availability check): not reached
- Kernel after latest reboot: not reached
- Installed dev/header package versions after latest upgrade: not reached
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: N/A - run stopped before clone creation
- Hostname/IP DHCP conversion: N/A - run stopped before clone creation
- CMC reinstall #1: N/A - run stopped before clone creation
- 10 GB source disk prep before first CMC install: N/A - run stopped before clone creation
- Local migration #1 (10GB -> 11GB) initial sync: N/A - run stopped before clone creation
- Step-up kernel upgrade: FAIL - source inspection found only one filtered kernel upgrade candidate
- Step-up dev/header package match check: N/A - not reached
- Online in skidamarink after step-up: N/A - not reached
- MTDI/Galaxy Migrate service+driver health after step-up: N/A - not reached
- Write data + tracking status: N/A - not reached
- CMC uninstall: N/A - not reached
- Latest kernel upgrade: N/A - not reached
- Latest dev/header package match check: N/A - not reached
- CMC reinstall #2: N/A - not reached
- Local migration #2 (10GB -> 11GB) initial sync: N/A - not reached
- Online in skidamarink after latest upgrade: N/A - not reached
- MTDI/Galaxy Migrate service+driver health after latest upgrade: N/A - not reached
- Clone power off and deletion (success path only): N/A - not reached
## Final Outcome
- Overall result: FAIL
- Blocking issue summary: the filtered Ubuntu 24.04 kernel candidate list contained only one upgrade target (`6.8.0-111.111`), so the test stopped before cloning per the test-file rule.
- Follow-up actions: update the Ubuntu package source or test target if a second kernel candidate is required for this workflow.
---
## Host Metadata ## Host Metadata
- Test date/time (UTC): 2026-05-15 16:26 UTC - Test date/time (UTC): 2026-05-15 16:26 UTC
- Operator: codex - Operator: codex

16
tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-summary.md
View File

@@ -49,3 +49,19 @@ Test file: `cmc-upgrade-kernel-test.md`
- Host tested: atvm148-redhat10.0 - Host tested: atvm148-redhat10.0
- Kernel progression: 6.12.0-55.9.1.el10_0.x86_64 -> 6.12.0-55.11.1.el10_0.x86_64 -> 6.12.0-124.56.1.el10_1.x86_64 - Kernel progression: 6.12.0-55.9.1.el10_0.x86_64 -> 6.12.0-55.11.1.el10_0.x86_64 -> 6.12.0-124.56.1.el10_1.x86_64
- Overall result: PASS - Overall result: PASS
## Ubuntu 24.04 - FAIL
- UTC date/time for the run: 2026-05-15 17:12 UTC
- Workflow summary: source inspection only; stopped before clone creation because the filtered kernel candidate list contained only one upgrade target
- Host tested: atvm121-ubuntu24.04
- Kernel progression: 6.8.0-31-generic -> 6.8.0-111.111 -> not reached
- Overall result: FAIL
## Ubuntu 24.04 - PASS
- UTC date/time for the run: 2026-05-15 17:39 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- Host tested: atvm121-ubuntu24.04
- Kernel progression: 6.8.0-31-generic -> 6.8.0-111-generic -> 6.8.0-117-generic
- Overall result: PASS