Red Hat Bugzilla – Bug 888312
Wrong auto-generated disk aliases when importing a VM with no alias
Last modified: 2016-02-10 14:00:14 EST
+++ This bug was initially created as a clone of Bug #882616 +++
Description of problem:
When a VM is imported from an OVF that does not contain disk aliases, the ImprotVM command auto-generates aliases.
However, these aliases are not generated correctly. For a VM with N disks, the aliases should be VmName_Disk1, VmName_Disk2, etc. up to VmName_DiskN.
Instead, ALL the disks are called VmName_DiskN.
Note that when an OVF is created by exporting a VM from 3.1, it will have disk aliases, so this bug will not be relevant.
However, OVFs exported from 3.0, or created by ESXi 5.1 and then translated with v2v will have this issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a VM with 3 disks.
2. Manually edit the OVF, and remove the disk:alias properties (see explanation above).
3. Remove the original VM
4. Import the OVF
All the disks will have the alias VmName_Disk3.
The disks should have the following aliases: VmName_Disk1, VmName_Disk2 and VmName_Disk3.
--- Additional comment from Allon Mureinik on 2012-12-02 09:37:24 EST ---
Sent patch Ibdd6525529d3d5e0c8ee2c86b418562929118207 for review:
--- Additional comment from Allon Mureinik on 2012-12-18 06:36:45 EST ---
verified on sf27