Created attachment 1383909 [details] logs and video capture Description of problem: When changing data center in new direct LUN prompt, the iSCSI targets view is not refreshed, hence, wrong iSCSI targets list is presented for the picked data center Version-Release number of selected component (if applicable): Found in both 4.1 and 4.2 rhvm-4.2.1.1-0.1.el7.noarch rhevm-4.1.9.1-0.1.el7.noarch How reproducible: Always Steps to Reproduce: 1. Have 2 initialized and active data centers, on each one, have the hosts connected to different iSCSI targets 2. Open new direct LUN prompt and change the data center field Actual results: iSCSI targets list is not refreshed when changing the DC Expected results: iSCSI targets list should get refreshed upon DC change in new direct LUN prompt Additional info: logs and video capture 2018-01-21 12:27:57,417+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (default task-27) [b28af667-5c41-4725-8b55-4613a426c401] START, GetDeviceListVDSCommand(HostName = host_mixed_1, GetDeviceListVDSCommandParameters:{hostId='cb218308-eb22-4985-a475-e0877556782c', storageType='ISCSI', checkStatus='false', lunIds='null'}), log id: 32435118 In the video capture, iSCSI targets lists are compared between new direct LUN and new storage domain prompts. In new storage domain prompt, the list is refreshed upon DC change.
It seems that bug also happens on RHVM 4.1.8.2-0.1.el7 So I guess it's not a regression. Tal, can we postpone it to 4.3.0?
Yes, for the slightest chance it might have been a regression from the new changes in the dialog I've suggested 4.2.1 but since it's not a regression 4.3 is the correct version
LUNs and targets view is being refreshed upon navigation between data centers in new direct LUN prompt. Used: ovirt-engine-4.3.0-0.0.master.20180815091554.gitd5455ea.el7.noarch
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.