An OpenShift cluster running version 4.18.19 with OpenShift Virtualization v4.18.8 fails to migrate VMs when the VM name exceeds 47 characters.

This issue is similar to CNV-61066, which was addressed by updating the "Known Issues" section in the release notes for versions 4.14+. 

However, we are opening this Jira because the same operation works successfully in OpenShift version 4.12.35 with OpenShift Virtualization v4.12.10. I will attach a screenshot from the customer showing a successful live migration of a VM with a 63-character name in that version.


Based on the events, the migration process appends a 16-character string ("-migration-XXXXX") to the VM name, which appears to be the root cause of the current name limit.

Given that this behavior changed between versions 4.12 and 4.18, could you please confirm if this is a bug or the expected result of a new PR?

CNV 4.18.8

1. Create a VM and set it's name with 48 characters. e.g: vm0123456789abcdefghijklmnopqrstuvwxyz01234567892. 

2. Let it running and Click "Migrate", nothing will happen. 

3. if using the name with 47 characters, it will be successful. 
e.g: finevm0123456789abcdefghijklmnopqrstuvwxyz012345678 

vm0123456789abcdefghijklmnopqrstuvwxyz0123456789: not work
vm0123456789abcdefghijklmnopqrstuvwxyz012345678: work

vm0123456789abcdefghijklmnopqrstuvwxyz0123456789: work vm0123456789abcdefghijklmnopqrstuvwxyz012345678: work

# oc describe vmi vm0123456789abcdefghijklmnopqrstuvwxyz0123456789

...
Events:
  Type     Reason            Age                   From                         Message
  ----     ------            ----                  ----                         -------
  Normal   SuccessfulCreate  61m                   disruptionbudget-controller  Created PodDisruptionBudget kubevirt-disruption-budget-jpqd5
  Normal   SuccessfulCreate  61m                   virtualmachine-controller    Created virtual machine pod virt-launcher-vm0123456789abcdefghijklmnopqrstuvwxyz0123454st78
  Normal   Created           61m                   virt-handler                 VirtualMachineInstance defined.
  Normal   Started           61m                   virt-handler                 VirtualMachineInstance started.
  Warning  FailedUpdate      59m (x15 over 60m)    virtualmachine-controller    Error expanding the PodDisruptionBudget kubevirt-disruption-budget-jpqd5: PodDisruptionBudget.policy "kubevirt-disruption-budget-jpqd5" is invalid: metadata.labels: Invalid value: "vm0123456789abcdefghijklmnopqrstuvwxyz0123456789-migration-rhiau": must be no more than 63 characters
  Warning  FailedUpdate      46m (x16 over 49m)    virtualmachine-controller    Error expanding the PodDisruptionBudget kubevirt-disruption-budget-jpqd5: PodDisruptionBudget.policy "kubevirt-disruption-budget-jpqd5" is invalid: metadata.labels: Invalid value: "vm0123456789abcdefghijklmnopqrstuvwxyz0123456789-migration-9xpju": must be no more than 63 characters
  Warning  FailedUpdate      6m16s (x20 over 44m)  virtualmachine-controller    Error expanding the PodDisruptionBudget kubevirt-disruption-budget-jpqd5: PodDisruptionBudget.policy "kubevirt-disruption-budget-jpqd5" is invalid: metadata.labels: Invalid value: "vm0123456789abcdefghijklmnopqrstuvwxyz0123456789-migration-4uf8z": must be no more than 63 characters