test: skip StorageClassMigration when VD Migration Controller reverts volume migration

[universal-itengineer]

Description

Skip StorageClassMigration e2e tests when VD Migration Controller reverts volume migration.

Changes:

• New SkipIfVDMigrationReverted function in test/e2e/internal/util/vm.go: checks vd.Status.MigrationState for Result=Failed with Message="Migration reverted." and skips the test if found.
• Added SkipIfVDMigrationReverted calls inside polling loops in:
  • UntilVMMigrationSucceeded
  • untilVirtualDisksMigrationsSucceeded
  • "two migrations in a row" test in volume_migration_storage_class_changed.go
• Minor fix: replaced Expect(err).NotTo(HaveOccurred()) with return err inside Eventually(func() error {...}) callback to properly propagate errors instead of failing immediately.

Why do we need it, and what problem does it solve?

VD Migration Controller may revert an in-progress volume migration for various reasons (VM not running, VM not migrating, etc.). When this happens, e2e tests polling for migration success wait until timeout and then fail, even though the migration was intentionally reverted by the controller. This creates flaky test failures unrelated to actual code defects.

What is the expected result?

During polling, if any VirtualDisk in the namespace has MigrationState.Result=Failed and MigrationState.Message="Migration reverted.", the test is immediately skipped with a clear message instead of waiting for timeout and failing.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries