Description of problem: Disk alias recycling in web-admin portal Version-Release number of selected component (if applicable): 3.2 How reproducible: Always Steps to Reproduce: 1) Create VM with single disk. (Disk Tab shows disk server_Disk1) 2) Add another disk. (Disk Tab shows disk server_Disk1 and server_Disk2) 3) Delete orginal disk (Disk Tab shows disk server_Disk2) 4) Add another disk (Disk Tab shows disk server_Disk2 and server_Disk2) Actual results: (Disk Tab shows disk server_Disk2 and server_Disk2) Expected results: Disk creation dialog provides warning and does not permit two disks of the same alias. Perhaps suggests new alias based on an incremental counter. Additional info:
Disk aliases are not unique by design. There is for example no reason to limit 2 disks attached to different VMs from having the same alias (e.g. disk1). Preventing dups would mean that you could not detach both of these disks without changing the alias of at least one of them which seems a bit limiting. However, when giving an automatic alias to a disk attached to a vm, it should not be the same as another disk that is already attached.
Failed basic flow - no recycling. Steps to Reproduce: 1) Create VM with single disk. (Disk Tab shows disk server_Disk1) 2) Add another disk. (Disk Tab shows disk server_Disk1 and server_Disk2) 3) Delete orginal disk (Disk Tab shows disk server_Disk2) 4) Add another disk results - we got server_Disk3 instead of server_Disk1 again.
verified using vt2.2 https://tcms.engineering.redhat.com/run/163712/
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, 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://rhn.redhat.com/errata/RHSA-2015-0158.html