Description of problem: As of now the diskMappings uses disk 'id'. This disk id is fetched via VMware SDK. To ease the user, Sam Lucidi suggested: "The diskMapping will accept a name, but it uses the device label which is hard to get without the SDK. I will see if I can change it to use the name that appears in the UI, e.g. Hard disk 1" Version-Release number of selected component (if applicable): CNV-2.5: iib-22696 hco-v2.5.0-396
Apparently this is already implemented. Turning this bug into a doc bug, to document upstream here: https://github.com/kubevirt/vm-import-operator/blob/master/examples/vmware/vmimport-internal-mapping.yaml#L25 And all the other occurences that might be for diskMappings. Need to add that both disk id or name can be provided. Also need to explain how to fetch them (name form VMware UI, and disk id from VMware sdk?).
https://github.com/kubevirt/vm-import-operator/pull/435
Verified on latest upstream doc: https://github.com/kubevirt/vm-import-operator/blob/master/docs/design.md https://github.com/kubevirt/vm-import-operator/blob/master/examples/vmware/vmimport-internal-mapping.yaml
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Virtualization 2.5.2 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:5560