-
Bug
-
Resolution: Unresolved
-
Critical
-
CNV v4.21.0
-
None
-
Quality / Stability / Reliability
-
3
-
False
-
-
False
-
None
-
Release Notes
-
-
Known Issue
-
Proposed
-
-
CNV Storage Sprint 283
-
Important
-
None
Description of problem:
Created multi-ns Plan and Migration with long names + namespace name is very long - VirtualMachineStorageMigration is stuck in BeginLiveMigration phase.
$ oc logs -n openshift-cnv kubevirt-migration-controller-68d7d479c5-b4pk5 | grep ERROR
2026-01-22T09:06:58Z ERROR Reconciler error {"controller": "kubevirt-storage-migration-controller", "object": {"name":"storage-mig-plan-rn27-storage-migration-test-storage-class-migration","namespace":"storage-migration-test-storage-class-migration"}, "namespace": "storage-migration-test-storage-class-migration", "name": "storage-mig-plan-rn27-storage-migration-test-storage-class-migration", "reconcileID": "ac2a9309-a937-423f-873e-a738e426d035", "error": "DataVolume.cdi.kubevirt.io \"fedora-1769072383-34219-mig-mt7k\" is invalid: metadata.labels: Invalid value: \"storage-mig-plan-rn27-storage-migration-test-storage-class-migration\": must be no more than 63 characters"}
Version-Release number of selected component (if applicable):
4.21.0
How reproducible:
Alwyas
Steps to Reproduce:
$ oc get MultiNamespaceVirtualMachineStorageMigrationPlan -A NAMESPACE NAME AGE storage-migration-test-storage-class-migration storage-mig-plan-rn27 4m48s $ oc get MultiNamespaceVirtualMachineStorageMigration -A NAMESPACE NAME PLAN PHASE AGE storage-migration-test-storage-class-migration migration-storage-mig-plan-rn27 storage-mig-plan-rn27 5m30s
Migration is stuck in BeginLiveMigration phase:
$ oc get VirtualMachineStorageMigration -A NAMESPACE NAME PLAN PHASE AGE storage-migration-test-storage-class-migration storage-mig-plan-rn27-storage-migration-test-storage-class-migration storage-mig-plan-rn27-storage-migration-test-storage-class-migration BeginLiveMigration 6m7s
Actual results:
Migration stuck in BeginLiveMigration
Expected results:
Migration succeeds (and error propagation to the resource would be nice)
Additional info: