Created attachment 1327372 [details] screenshot Description of problem: When trying to add new iSCSI storage domain, and selecting a target, the list of exposed LUNs is empty Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20170915203601.git96df02d.el7.centos How reproducible: 100% Steps to Reproduce: 1. Try to add new iSCSI storage domain 2. 3. Actual results: The list of exposed LUNs is empty Expected results: Additional info: screenshot attached
Alexander - this also looks related to the recent work on grids. Could you take a look please?
Raz - can you re-test with the latest bits?
Tested on 4.2.0-0.0.master.20170918173214.git7183359.el7.centos and the issue still exists. A workaround is to select "LUNs -> Targets" in the dialog box (screenshot attached)
Created attachment 1327941 [details] screenshot for workaround
(In reply to Raz Tamir from comment #3) > Tested on 4.2.0-0.0.master.20170918173214.git7183359.el7.centos and the > issue still exists. > > A workaround is to select "LUNs -> Targets" in the dialog box (screenshot > attached) This also looks horrible (I guess there's some problem with the CSS there?), but at least it's usable. If this is the ONLY issue we have on alpha perhaps it's not worth blocking on that, but considering users don't usually upgrade to an alpha version but use it on a different, new, system just to check it out, I think this is a really bad first impression.
blocking oVirt 4.2.0 Alpha release on this.
As there is a workaround for this issue, see commnt 3,lowering severity
I have the LUNs > Targets working right now, but there is an issue with Targets > LUNs that I am still working out. I should hopefully have that worked out some time today.
Verified on ovirt-engine-4.2.0-0.0.master.20170921184504.gitfcfc9a7.el7.centos Add iSCSI storage domain from Targets -> LUNs works fine
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.