Undefined Description of problem:
When trying to use the following pvcNameTemplate, the plan shows up as "Not Ready" if the source VM contains upper case characters:
pvcNameTemplate: '{{.VmName}}-disk-{{.DiskIndex}}'
pvcNameTemplateUseGenerateName: false
While VM names should be lowercase in OpenShift, they are renamed during the migration. The pvcNameTemplate does not appear to be doing the same.
Note this works on 2.8.6, but fails to allow the plan to start on 2.9.3
Version-Release number of selected component (if applicable):
MTV 2.9.3
How reproducible:
100%
Steps to Reproduce:
1. Ensure source VM in vmware has capital letters (All caps is what we've tested)
2. Create a plan with the following in the spec:
pvcNameTemplate: '{{.VmName}}-disk-{{.DiskIndex}}' pvcNameTemplateUseGenerateName: false
Actual results:
Plan shows "Not Ready" with status of
status:
conditions:
- category: Critical
items:
- ' id:vm-20050 name:''UPPERCASEVM'' template:{{.VmName}}-disk-{{.DiskIndex}}
error:Template output is invalid k8s label [UPPERCASEVM-disk-0]'
lastTransitionTime: "2025-09-11T18:26:30Z"
message: VM PVC name template is invalid.
status: "True"
type: NotValid
migration: {}
observedGeneration: 1
Expected results:
The plan should succeed with the pvc taking on the lowercase conversion names just like the VM will
Additional info:
