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

Standardize test file header format

Browse Source
This commit is contained in:
Cirrus Codex
2026-05-15 13:09:17 -04:00
parent 142387ce5e
commit afc4475409
3 changed files with 344 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -236,6 +236,7 @@ Also generate a run summary file in the same directory:
- If a run is still in progress when first recorded, update the runtime once the run reaches its terminal outcome. - If a run is still in progress when first recorded, update the runtime once the run reaches its terminal outcome.
Summary file requirements: Summary file requirements:
- Start the file with the test file name line: `Test file: cmc-upgrade-kernel-test.md`
- Title: `CMC Upgrade Kernel Test Summary` - Title: `CMC Upgrade Kernel Test Summary`
- Include UTC date/time for the run - Include UTC date/time for the run
- Include total test duration for the run - Include total test duration for the run

292
tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-results.md Normal file
View File

@@ -0,0 +1,292 @@
Test file: `cmc-upgrade-kernel-test.md`
# CMC Upgrade Kernel Test Results
## Host Metadata
- Test date/time (UTC): 2026-05-13 23:32 UTC
- Operator: codex
- Source VM: atvm114-amazonlinux2023
- Cloned VM name: aw999-amazonlinux2023
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.136
## Kernel / OS Tracking
- Start OS version: Amazon Linux 2023
- Start kernel version: 6.1.61-85.141.amzn2023.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 6.1.168-202.320.amzn2023.x86_64, 6.1.168-203.330.amzn2023.x86_64
- Kernel selected for step-up upgrade: 6.1.168-202.320.amzn2023.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-6.1.168-202.320.amzn2023.x86_64, kernel-headers-6.1.168-202.320.amzn2023.x86_64
- Kernel after step-up reboot: 6.1.168-202.320.amzn2023.x86_64
- Installed dev/header package versions after step-up: kernel-6.1.61-85.141.amzn2023.x86_64, kernel-6.1.168-202.320.amzn2023.x86_64, kernel-devel-6.1.168-202.320.amzn2023.x86_64, kernel-headers-6.1.168-202.320.amzn2023.x86_64
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): 6.1.168-202.320.amzn2023.x86_64, 6.1.168-203.330.amzn2023.x86_64
- Kernel selected for latest upgrade: 6.1.168-203.330.amzn2023.x86_64
- Matching dev/header packages for latest target (availability check): kernel-devel-6.1.168-203.330.amzn2023.x86_64, kernel-headers-6.1.168-203.330.amzn2023.x86_64
- Kernel after latest reboot: 6.1.168-203.330.amzn2023.x86_64
- Installed dev/header package versions after latest upgrade: kernel-6.1.61-85.141.amzn2023.x86_64, kernel-6.1.168-202.320.amzn2023.x86_64, kernel-6.1.168-203.330.amzn2023.x86_64, kernel-devel-6.1.168-202.320.amzn2023.x86_64, kernel-devel-6.1.168-203.330.amzn2023.x86_64, kernel-headers-6.1.168-203.330.amzn2023.x86_64
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: PASS - clone `aw999-amazonlinux2023` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-amazonlinux2023`; guest was already on DHCP and retained `192.168.0.136`
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `49c9929b-8db6-4c50-beb3-8caa2539c2a2` reached TRACKING
- Step-up kernel upgrade: PASS - installed `6.1.168-202.320.amzn2023.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: PASS - host `aw999-amazonlinux2023` was online in CDC
- MTDI/Galaxy Migrate service+driver health after step-up: PASS - `mtdi-daemon` and `galaxy-migrate` were active
- Write data + tracking status: PASS - wrote sample data to `sdb` and the local session returned to TRACKING
- CMC uninstall: PASS - uninstall completed and the host fell out of CDC after cleanup
- Latest kernel upgrade: PASS - installed `6.1.168-203.330.amzn2023.x86_64`
- Latest dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- CMC reinstall #2: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #2 (10GB -> 11GB) initial sync: PASS - session `30789ed2-434c-4ca7-b566-bd6d7206f117` reached TRACKING
- Online in skidamarink after latest upgrade: PASS - host `aw999-amazonlinux2023` returned online in CDC after reinstall
- MTDI/Galaxy Migrate service+driver health after latest upgrade: PASS - `mtdi-daemon` and `galaxy-migrate` were active
- Clone power off and deletion (success path only): PASS - VM was powered off and destroyed in vCenter, then the offline CDC host entry was removed on the next cleanup pass
## Final Outcome
- Overall result: PASS
- Blocking issue summary: none
- Follow-up actions: none
---
## Host Metadata
- Test date/time (UTC): 2026-05-15 16:26 UTC
- Operator: codex
- Source VM: atvm148-redhat10.0
- Cloned VM name: aw999-redhat10.0
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.96
## Kernel / OS Tracking
- Start OS version: Red Hat Enterprise Linux 10.0
- Start kernel version: 6.12.0-55.9.1.el10_0.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 6.12.0-55.11.1.el10_0, 6.12.0-55.14.1.el10_0, 6.12.0-55.43.1.el10_0, 6.12.0-124.56.1.el10_1
- Kernel selected for step-up upgrade: 6.12.0-55.11.1.el10_0.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-6.12.0-55.11.1.el10_0.x86_64, kernel-headers-6.12.0-55.11.1.el10_0.x86_64
- Kernel after step-up reboot: 6.12.0-55.11.1.el10_0.x86_64
- Installed dev/header package versions after step-up: kernel-6.12.0-55.9.1.el10_0.x86_64, kernel-6.12.0-55.11.1.el10_0.x86_64, kernel-devel-6.12.0-55.9.1.el10_0.x86_64, kernel-devel-6.12.0-55.11.1.el10_0.x86_64, kernel-headers-6.12.0-55.11.1.el10_0.x86_64
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): 6.12.0-55.11.1.el10_0, 6.12.0-55.14.1.el10_0, 6.12.0-55.43.1.el10_0, 6.12.0-124.56.1.el10_1
- Kernel selected for latest upgrade: 6.12.0-124.56.1.el10_1.x86_64
- Matching dev/header packages for latest target (availability check): kernel-devel-6.12.0-124.56.1.el10_1.x86_64, kernel-headers-6.12.0-124.56.1.el10_1.x86_64
- Kernel after latest reboot: 6.12.0-124.56.1.el10_1.x86_64
- Installed dev/header package versions after latest upgrade: kernel-6.12.0-55.9.1.el10_0.x86_64, kernel-6.12.0-55.11.1.el10_0.x86_64, kernel-6.12.0-124.56.1.el10_1.x86_64, kernel-devel-6.12.0-55.9.1.el10_0.x86_64, kernel-devel-6.12.0-55.11.1.el10_0.x86_64, kernel-devel-6.12.0-124.56.1.el10_1.x86_64, kernel-headers-6.12.0-124.56.1.el10_1.x86_64
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: PASS - clone `aw999-redhat10.0` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-redhat10-0`; networking was moved to DHCP and the clone came back on `192.168.0.96`
- 10 GB source disk prep before first CMC install: PASS - `/dev/sdb` was zeroed with `dd` and verified signature-free before the first CMC install
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `4692cdbb-8d2d-42f8-9da1-2b9fa0159ed6` reached TRACKING
- Step-up kernel upgrade: PASS - installed `6.12.0-55.11.1.el10_0.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: PASS - host `aw999-redhat10-0` was 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 sample data to `sdb` and the local session returned to TRACKING
- CMC uninstall: PASS - uninstall completed cleanly, then the stale CDC host entry was cleaned up
- Latest kernel upgrade: PASS - installed `6.12.0-124.56.1.el10_1.x86_64`
- Latest dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- CMC reinstall #2: PASS - host re-registered in CDC on the latest kernel
- Local migration #2 (10GB -> 11GB) initial sync: PASS - session `5b85940c-f243-43d9-8e04-301bfce9cca2` reached TRACKING
- Online in skidamarink after latest upgrade: PASS - host `aw999-redhat10-0` 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 and destroyed in vCenter, then 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 14:44 UTC
- Operator: codex
- Source VM: atvm70-redhat9.0
- Cloned VM name: aw999-redhat9.0
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.73
## Kernel / OS Tracking
- Start OS version: Red Hat Enterprise Linux 9.0
- Start kernel version: 5.14.0-70.22.1.el9_0.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 5.14.0-70.30.1.el9_0, 5.14.0-611.55.1.el9_7
- Kernel selected for step-up upgrade: 5.14.0-70.30.1.el9_0.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-5.14.0-70.30.1.el9_0.x86_64, kernel-headers-5.14.0-70.30.1.el9_0.x86_64
- Kernel after step-up reboot: 5.14.0-70.30.1.el9_0.x86_64
- Installed dev/header package versions after step-up: kernel-5.14.0-70.22.1.el9_0.x86_64, kernel-5.14.0-70.30.1.el9_0.x86_64, kernel-devel-5.14.0-70.22.1.el9_0.x86_64, kernel-devel-5.14.0-70.30.1.el9_0.x86_64, kernel-headers-5.14.0-70.30.1.el9_0.x86_64
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): 5.14.0-611.55.1.el9_7
- Kernel selected for latest upgrade: 5.14.0-611.55.1.el9_7.x86_64
- Matching dev/header packages for latest target (availability check): kernel-devel-5.14.0-611.55.1.el9_7.x86_64, kernel-headers-5.14.0-611.55.1.el9_7.x86_64
- Kernel after latest reboot: 5.14.0-611.55.1.el9_7.x86_64
- Installed dev/header package versions after latest upgrade: kernel-5.14.0-70.22.1.el9_0.x86_64, kernel-5.14.0-70.30.1.el9_0.x86_64, kernel-5.14.0-611.55.1.el9_7.x86_64, kernel-devel-5.14.0-70.22.1.el9_0.x86_64, kernel-devel-5.14.0-70.30.1.el9_0.x86_64, kernel-devel-5.14.0-611.55.1.el9_7.x86_64, kernel-headers-5.14.0-611.55.1.el9_7.x86_64
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: PASS - clone `aw999-redhat9.0` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-redhat9-0`; networking was moved to DHCP and the clone came back on `192.168.0.73`
- One-time disk prep before first CMC install: PASS - `/dev/sdb` was wiped with `dd` and verified signature-free before the first CMC install
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `7180baa3-67e9-4789-9b54-eaa349ee6849` reached TRACKING
- Step-up kernel upgrade: PASS - installed `5.14.0-70.30.1.el9_0.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: PASS - host `aw999-redhat9-0` was connected in CDC
- MTDI/Galaxy Migrate service+driver health after step-up: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi_nexus` were healthy
- Write data + tracking status: PASS - wrote sample data to `sdb` and the local session returned to TRACKING
- CMC uninstall: PASS - `mtdi-daemon` and `galaxy-migrate` were removed cleanly
- Latest kernel upgrade: PASS - installed `5.14.0-611.55.1.el9_7.x86_64`
- Latest dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- CMC reinstall #2: PASS - host re-registered in CDC on the latest kernel after building `mtdi-nexus` with gcc-toolset-15
- Local migration #2 (10GB -> 11GB) initial sync: PASS - session `51632a28-061c-436d-a4b3-9662b8e40f66` reached TRACKING
- Online in skidamarink after latest upgrade: PASS - host `aw999-redhat9-0` was connected in CDC after reinstall
- MTDI/Galaxy Migrate service+driver health after latest upgrade: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi_nexus` were healthy
- Clone power off and deletion (success path only): PASS - VM was powered off and destroyed in vCenter, then 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-14 00:14 UTC
- Operator: codex
- Source VM: atvm26-centos7.9
- Cloned VM name: aw999-centos7.9
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.3.239
## Kernel / OS Tracking
- Start OS version: CentOS Linux 7.9.2009
- Start kernel version: 3.10.0-1160.el7.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 3.10.0-1160.118.1.el7, 3.10.0-1160.119.1.el7
- Kernel selected for step-up upgrade: 3.10.0-1160.118.1.el7.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-3.10.0-1160.118.1.el7.x86_64, kernel-headers-3.10.0-1160.118.1.el7.x86_64
- Kernel after step-up reboot: 3.10.0-1160.118.1.el7.x86_64
- Installed dev/header package versions after step-up: kernel-3.10.0-1160.el7.x86_64, kernel-3.10.0-1160.118.1.el7.x86_64, kernel-devel-3.10.0-1160.el7.x86_64, kernel-devel-3.10.0-1160.118.1.el7.x86_64, kernel-headers-3.10.0-1160.118.1.el7.x86_64
- 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: PASS - clone `aw999-centos7.9` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-centos7-9`; networking was moved to DHCP and the clone came back on `192.168.3.239`
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `d4386203-5e1b-4140-b159-3a1b310caa5f` reached TRACKING
- Step-up kernel upgrade: PASS - installed `3.10.0-1160.118.1.el7.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: FAIL - CDC remained offline after reboot and service restart attempts
- MTDI/Galaxy Migrate service+driver health after step-up: FAIL - `mtdi-daemon` repeatedly core-dumped on start while `galaxy-migrate` stayed active
- Write data + tracking status: N/A - not reached after blocker
- CMC uninstall: N/A - not reached after blocker
- Latest kernel upgrade: N/A - not reached after blocker
- Latest dev/header package match check: N/A - not reached after blocker
- CMC reinstall #2: N/A - not reached after blocker
- Local migration #2 (10GB -> 11GB) initial sync: N/A - not reached after blocker
- Online in skidamarink after latest upgrade: N/A - not reached after blocker
- MTDI/Galaxy Migrate service+driver health after latest upgrade: N/A - not reached after blocker
- Clone power off and deletion (success path only): N/A - blocker occurred after clone creation; VM left powered on for inspection
## Final Outcome
- Overall result: FAIL
- Blocking issue summary: `mtdi-daemon` core-dumped immediately after the step-up reboot on CentOS 7.9 and could not be stabilized with service restarts.
- Follow-up actions: Inspect `journalctl -u mtdi-daemon` and the core dump on the clone, then compare the failure against the 3.10.0-1160.118.1.el7 kernel path before attempting the next upgrade stage.
---
## Host Metadata
- Test date/time (UTC): 2026-05-14 01:17 UTC
- Operator: codex
- Source VM: atvm26-centos7.9
- Cloned VM name: aw999-centos7.9
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.73
## Kernel / OS Tracking
- Start OS version: CentOS Linux 7.9.2009
- Start kernel version: 3.10.0-1160.el7.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 3.10.0-1160.118.1.el7, 3.10.0-1160.119.1.el7
- Kernel selected for step-up upgrade: 3.10.0-1160.118.1.el7.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-3.10.0-1160.118.1.el7.x86_64, kernel-headers-3.10.0-1160.118.1.el7.x86_64
- Kernel after step-up reboot: 3.10.0-1160.118.1.el7.x86_64
- Installed dev/header package versions after step-up: kernel-3.10.0-1160.el7.x86_64, kernel-3.10.0-1160.118.1.el7.x86_64, kernel-devel-3.10.0-1160.el7.x86_64, kernel-devel-3.10.0-1160.118.1.el7.x86_64, kernel-headers-3.10.0-1160.118.1.el7.x86_64
- 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: PASS - clone `aw999-centos7.9` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-centos7-9`; networking was moved to DHCP and the clone came back on `192.168.0.73`
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `0da4c9fd-b10f-443a-a189-27e73412a21a` reached TRACKING
- Step-up kernel upgrade: PASS - installed `3.10.0-1160.118.1.el7.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: FAIL - CDC host entry dropped offline after reboot
- MTDI/Galaxy Migrate service+driver health after step-up: FAIL - `mtdi-daemon` core-dumped on start and `mtdi-driver.service` was blocked by a stale `ConditionPathExists` path; `galaxy-migrate` stayed active
- Write data + tracking status: N/A - not reached after blocker
- CMC uninstall: N/A - not reached after blocker
- Latest kernel upgrade: N/A - not reached after blocker
- Latest dev/header package match check: N/A - not reached after blocker
- CMC reinstall #2: N/A - not reached after blocker
- Local migration #2 (10GB -> 11GB) initial sync: N/A - not reached after blocker
- Online in skidamarink after latest upgrade: N/A - not reached after blocker
- MTDI/Galaxy Migrate service+driver health after latest upgrade: N/A - not reached after blocker
- Clone power off and deletion (success path only): N/A - blocker occurred after clone creation; VM left powered on for inspection
## Final Outcome
- Overall result: FAIL
- Blocking issue summary: post-reboot `mtdi-daemon` aborts immediately on CentOS 7.9 after the step-up kernel install, and `mtdi-driver.service` does not start because its condition points at `/lib/modules/3.10.0-1160.118.1.el7.x86_64/extra/mtdi-nexus.ko` instead of the weak-updates path where the module exists.
- Follow-up actions: compare the unit-file path check with the installed module layout on the step-up kernel before attempting the next stage
---
## Host Metadata
- Test date/time (UTC): 2026-05-15 00:15 UTC
- Operator: codex
- Source VM: atvm16-centos6.10
- Cloned VM name: aw999-centos6.10
- Clone origin (vCenter path/folder/cluster): /CDSHQ-Eng/vm / AutomatedTest-UnitTesting / QACL-ATVMCypressONLY
- Final DHCP IP of clone: 192.168.0.54
## Kernel / OS Tracking
- Start OS version: CentOS Linux 6.10
- Start kernel version: 2.6.32-754.el6.x86_64
- Kernel list before first upgrade (full candidate list, filtered by scope rule): 2.6.32-754.2.1.el6, 2.6.32-754.3.5.el6, 2.6.32-754.6.3.el6, 2.6.32-754.9.1.el6, 2.6.32-754.10.1.el6, 2.6.32-754.11.1.el6, 2.6.32-754.12.1.el6, 2.6.32-754.14.2.el6, 2.6.32-754.15.3.el6, 2.6.32-754.17.1.el6, 2.6.32-754.18.2.el6, 2.6.32-754.22.1.el6, 2.6.32-754.23.1.el6, 2.6.32-754.24.2.el6, 2.6.32-754.24.3.el6, 2.6.32-754.25.1.el6, 2.6.32-754.27.1.el6, 2.6.32-754.28.1.el6, 2.6.32-754.29.1.el6, 2.6.32-754.29.2.el6, 2.6.32-754.30.2.el6, 2.6.32-754.31.1.el6, 2.6.32-754.33.1.el6, 2.6.32-754.35.1.el6
- Kernel selected for step-up upgrade: 2.6.32-754.2.1.el6.x86_64
- Matching dev/header packages for step-up target (availability check): kernel-devel-2.6.32-754.2.1.el6.x86_64, kernel-headers-2.6.32-754.2.1.el6.x86_64
- Kernel after step-up reboot: 2.6.32-754.2.1.el6.x86_64
- Installed dev/header package versions after step-up: kernel-2.6.32-754.el6.x86_64, kernel-2.6.32-754.2.1.el6.x86_64, kernel-devel-2.6.32-754.el6.x86_64, kernel-devel-2.6.32-754.2.1.el6.x86_64, kernel-headers-2.6.32-754.2.1.el6.x86_64
- Kernel list before latest upgrade (full candidate list, filtered by scope rule): 2.6.32-754.2.1.el6, 2.6.32-754.3.5.el6, 2.6.32-754.6.3.el6, 2.6.32-754.9.1.el6, 2.6.32-754.10.1.el6, 2.6.32-754.11.1.el6, 2.6.32-754.12.1.el6, 2.6.32-754.14.2.el6, 2.6.32-754.15.3.el6, 2.6.32-754.17.1.el6, 2.6.32-754.18.2.el6, 2.6.32-754.22.1.el6, 2.6.32-754.23.1.el6, 2.6.32-754.24.2.el6, 2.6.32-754.24.3.el6, 2.6.32-754.25.1.el6, 2.6.32-754.27.1.el6, 2.6.32-754.28.1.el6, 2.6.32-754.29.1.el6, 2.6.32-754.29.2.el6, 2.6.32-754.30.2.el6, 2.6.32-754.31.1.el6, 2.6.32-754.33.1.el6, 2.6.32-754.35.1.el6
- Kernel selected for latest upgrade: 2.6.32-754.35.1.el6.x86_64
- Matching dev/header packages for latest target (availability check): kernel-devel-2.6.32-754.35.1.el6.x86_64, kernel-headers-2.6.32-754.35.1.el6.x86_64
- Kernel after latest reboot: 2.6.32-754.35.1.el6.x86_64
- Installed dev/header package versions after latest upgrade: kernel-2.6.32-754.el6.x86_64, kernel-2.6.32-754.2.1.el6.x86_64, kernel-2.6.32-754.35.1.el6.x86_64, kernel-devel-2.6.32-754.el6.x86_64, kernel-devel-2.6.32-754.2.1.el6.x86_64, kernel-devel-2.6.32-754.35.1.el6.x86_64, kernel-headers-2.6.32-754.35.1.el6.x86_64
## Execution Summary (Short Bullets)
- Clone created / FC PCI detached: PASS - clone `aw999-centos6.10` created on `AutomatedTest-UnitTesting`; both FC passthrough devices were removed before guest work
- Hostname/IP DHCP conversion: PASS - hostname set to `aw999-centos6-10`; networking was moved to DHCP and the clone came back on `192.168.0.54`
- 10 GB source disk prep before first CMC install: PASS - `/dev/sdb` was wiped and verified signature-free before the first CMC install
- CMC reinstall #1: PASS - installed with `-no-prebuilt-mtdi-nexus`
- Local migration #1 (10GB -> 11GB) initial sync: PASS - session `d7a2f7c3-22ab-4ece-b4fe-1c56601980f6` reached TRACKING
- Step-up kernel upgrade: PASS - installed `2.6.32-754.2.1.el6.x86_64`
- Step-up dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- Online in skidamarink after step-up: PASS - host `aw999-centos6-10` was connected in CDC
- MTDI/Galaxy Migrate service+driver health after step-up: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi_nexus` were healthy
- Write data + tracking status: PASS - wrote sample data to `sdb` and the local session returned to TRACKING
- CMC uninstall: PASS - `mtdi-daemon` and `galaxy-migrate` were removed cleanly
- Latest kernel upgrade: PASS - installed `2.6.32-754.35.1.el6.x86_64`
- Latest dev/header package match check: PASS - matching `kernel-devel` and `kernel-headers` were present
- CMC reinstall #2: PASS - host re-registered in CDC on the latest kernel
- Local migration #2 (10GB -> 11GB) initial sync: PASS - session `672450f6-fb3a-490b-bbc6-ba5c7c359f68` reached TRACKING
- Online in skidamarink after latest upgrade: PASS - host `aw999-centos6-10` was connected in CDC after reinstall
- MTDI/Galaxy Migrate service+driver health after latest upgrade: PASS - `mtdi-daemon`, `galaxy-migrate`, and `mtdi_nexus` were healthy
- Clone power off and deletion (success path only): PASS - VM was powered off and destroyed in vCenter, then the offline CDC host entry was removed on cleanup
## Final Outcome
- Overall result: PASS
- Blocking issue summary: none
- Follow-up actions: none

51
tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-summary.md Normal file
View File

@@ -0,0 +1,51 @@
Test file: `cmc-upgrade-kernel-test.md`
# CMC Upgrade Kernel Test Summary
## Amazon Linux 2023 - PASS
- UTC date/time for the run: 2026-05-13 23:32 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- Host tested: atvm114-amazonlinux2023
- Kernel progression: 6.1.61-85.141.amzn2023.x86_64 -> 6.1.168-202.320.amzn2023.x86_64 -> 6.1.168-203.330.amzn2023.x86_64
- Overall result: PASS
## CentOS 7.9 - FAIL
- UTC date/time for the run: 2026-05-14 00:14 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- Host tested: atvm26-centos7.9
- Kernel progression: 3.10.0-1160.el7.x86_64 -> 3.10.0-1160.118.1.el7.x86_64 -> not reached
- Overall result: FAIL
## CentOS 7.9 Follow-Up - FAIL
- UTC date/time for the run: 2026-05-14 01:17 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> stop at service-health blocker before sample-data sync
- Host tested: atvm26-centos7.9
- Kernel progression: 3.10.0-1160.el7.x86_64 -> 3.10.0-1160.118.1.el7.x86_64 -> not reached
- Overall result: FAIL
## CentOS 6.10 - PASS
- UTC date/time for the run: 2026-05-15 00:15 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- Host tested: atvm16-centos6.10
- Kernel progression: 2.6.32-754.el6.x86_64 -> 2.6.32-754.2.1.el6.x86_64 -> 2.6.32-754.35.1.el6.x86_64
- Overall result: PASS
## Red Hat 9.0 - PASS
- UTC date/time for the run: 2026-05-15 14:44 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- Host tested: atvm70-redhat9.0
- Kernel progression: 5.14.0-70.22.1.el9_0.x86_64 -> 5.14.0-70.30.1.el9_0.x86_64 -> 5.14.0-611.55.1.el9_7.x86_64
- Overall result: PASS
## Red Hat 10.0 - PASS
- UTC date/time for the run: 2026-05-15 16:26 UTC
- Workflow summary: current kernel -> install CMC -> kernel upgrade -> uninstall CMC -> kernel upgrade -> install CMC
- 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
- Overall result: PASS