|Summary:||While managing a block storage domain, moving too fast to Targets > LUNs table resets lun's isInclude() check-mark|
|Product:||[oVirt] ovirt-engine||Reporter:||shani <sleviim>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Natalie Gavrielov <ngavrilo>|
|Version:||4.2.0||CC:||bugs, ratamir, tnisan, ylavi|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-02-12 11:51:57 UTC||Type:||Bug|
|oVirt Team:||Storage||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description shani 2017-11-22 15:09:25 UTC
Created attachment 1357597 [details] When moving to Targets > LUNs table immediately, the storage domain's included luns can't been detected. Description of problem: When managing a block storage domain, the opened dialogue shows LUNs > Targets table. In case of moving to Targets > LUNs table immediately, the storage domain's included luns can't been detected (there's no green V next to them). Also, in case the lun can be extended, it has no longer an 'available size'. Version-Release number of selected component (if applicable): 4.2.0 How reproducible: 100% Steps to Reproduce: 1. Manage an isaci data storage domain 2. Wait until dialogue is fully uploaded and notice the included luns on LUNs > Targets table. 3. Close the dialogue and re-open it with clicking immediately on Targts > LUNs 4. Switch back to LUNs > Targets table. Actual results: There's no green V next to the included luns, and also there's no available size for extending. Expected results: Data should appear as before. Additional info: See attached gif for visualization.
Comment 1 Natalie Gavrielov 2018-02-06 14:51:41 UTC
Verified using rhvm-18.104.22.168-0.1.el7.noarch
Comment 2 Sandro Bonazzola 2018-02-12 11:51:57 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 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.