Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-2244

virtualmachine-validator failed after migration with custom templates

XMLWordPrintable

    • Incidents & Support
    • 5
    • False
    • Hide

      None

      Show
      None
    • True

      Description of problem:

      Warm migrate vm from vSphere 8 with template settings:
      pvcNameTemplate: {{.PlanName}}-{{.VmName}}-{{if eq .DiskIndex .RootDiskIndex}}root{{else}}data{{end}}-{{.DiskIndex}}
      networkNameTemplate: {{if eq .NetworkType "pod"}}pod{{else}}multus-{{.NetworkNamespace}}-{{.NetworkName}}-{{.NetworkIndex}}{{end}}
      volumeNameTemplate: pvc-{{.PVCName}}-disk-{{.VolumeIndex}}
      
      VirtualMachineCreation phase, hit error:
      admission webhook "virtualmachine-validator.kubevirt.io" denied the request: must be no more than 63 characters, must be no more than 63 characters, must be no more than 63 characters, must be no more than 63 characters

      Version-Release number of selected component (if applicable):

      MTV 2.8.0-29 (IIB: 937321) with CNV 4.18.1

      How reproducible:

      Always

      Steps to Reproduce:

      1) Create warm migration plan: mtv-warm-win2022 to migrate vm: mtv-function-win2022-test from vSphere 8 to OCP cluster

      2) Set for the templates below and set the Preserve static IPs: on

      pvcNameTemplate: {{.PlanName}}-{{.VmName}}-{{if eq .DiskIndex .RootDiskIndex}}root{{else}}data{{end}}-{{.DiskIndex}}
      networkNameTemplate: {{if eq .NetworkType "pod"}}pod{{else}}multus-{{.NetworkNamespace}}-{{.NetworkName}}-{{.NetworkIndex}}{{end}}
      volumeNameTemplate: pvc-{{.PVCName}}-disk-{{.VolumeIndex}}

      3) Start the migration plan, it failed in VirtualMachineCreation phase, hit error:

      admission webhook "virtualmachine-validator.kubevirt.io" denied the request: must be no more than 63 characters, must be no more than 63 characters, must be no more than 63 characters, must be no more than 63 characters

      4) Check the PVC names:

      mtv-warm-win2022-mtv-function-win2022-test-root-0f99j4
      mtv-warm-win2022-mtv-function-win2022-test-data-1nqhmj
      mtv-warm-win2022-mtv-function-win2022-test-data-22jzxv
      mtv-warm-win2022-mtv-function-win2022-test-data-3lh8p6

      The PVC in VM yaml file will more than 63 characters

      pvc-mtv-warm-win2022-mtv-function-win2022-test-root-0f99j4-disk(63 characters)-0random_number

      Actual results:

      In step3, the migration plan failed to create the VM

      Expected results:

      In step3, the migration plan succeeded

      Additional info:

       

              yzamir@redhat.com Yaacov Zamir
              chhu@redhat.com Chenli Hu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: