kubeovn / kube-ovn / 21565852316

23%

master: 24%

Build Type

Pull #6243

github

Committed by zbb88888

Commit Message

fix: ensure kubevirt migration uses current migration state

Add MigrationUID validation to prevent stale state usage during
consecutive VM migrations (e.g., A→B→A).

Changes:
1. Add MigrationUID check: Only use vmi.Status.MigrationState if
   MigrationUID matches current vmiMigration.UID
2. Simplify MigrationScheduling: Wait for valid state instead of
   using Pod/vmi.Status.NodeName fallback
3. Add unit tests covering UID validation and migration scenarios

The root cause was that vmi.Status.MigrationState could contain stale
info from a previous migration, causing incorrect node detection and
skipping SetLogicalSwitchPortMigrateOptions.

Fixes: #6220
Signed-off-by: zbb88888 <jmdxjsjgcxy@gmail.com>

Pull Request Pull Request #6243: Fix migration

Coverage Stats

3 of 93 new or added lines in 2 files covered. (3.23%)

5 existing lines in 2 files now uncovered.

12332 of 53782 relevant lines covered (22.93%)

0.27 hits per line