Created attachment 1546792 [details] Screenshot Description of problem: Disk GUID is displayed instead of Disk name in the disks table while reconfiguring VM. Version-Release number of selected component (if applicable): 5.9 How reproducible: Always Steps to Reproduce: 1. Add a provider(in this case: RHEV). 2. Select a VM and click on `Configuration`. Select `Reconfigure the selected items` from the dropdown. 3. Check the `Disk Name` column in disks table. Actual results: Disk GUID is displayed. Expected results: Disk Name must be displayed Additional info:
This is possibly related and is a high severity regression https://bugzilla.redhat.com/show_bug.cgi?id=1692801
reproducer: 10.8.196.145 I think this is displaying the name and not the guid. I am attaching a screenshot of my vm with 2 disks. In Console, the Name appears to be correct. irb(main):006:0> v.hardware.disks.first => #<Disk id: 17, device_name: "win2012_temp_Disk1", device_type: "disk", location: "0", filename: "7a4a40a0-bf1a-447a-937c-a7334e3ff386", hardware_id: 21, mode: "persistent", controller_type: "virtio", size: 53687091200, free_space: nil, size_on_disk: 204800, present: true, start_connected: true, auto_detect: nil, created_on: "2019-03-27 20:07:48", updated_on: "2019-03-27 20:07:48", disk_type: "thin", storage_id: 1, backing_id: nil, backing_type: nil, storage_profile_id: nil, bootable: true> irb(main):007:0> v.hardware.disks.second => #<Disk id: 59, device_name: "billy_demo1_Disk2", device_type: "disk", location: "1", filename: "d3a32982-8e7c-458d-817e-b6bc117f40f0", hardware_id: 21, mode: "persistent", controller_type: "virtio", size: 22548578304, free_space: nil, size_on_disk: 0, present: true, start_connected: true, auto_detect: nil, created_on: "2019-03-28 13:26:44", updated_on: "2019-03-28 13:26:44", disk_type: "thick", storage_id: 1, backing_id: nil, backing_type: nil, storage_profile_id: nil, bootable: false> I think this BZ is related See BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1692801
The uuid is indeed displayed in the UI and used by the api, this is due to the fact that the disk name is not uniqe in rhv. You can have a vm with two disks with the same name. A fix would be perhaps to add an extra column for the name.