Bug 1560414

Summary: The textbox 'writethrough' in the subtab cache mode under tab configure lv cache is misleading.
Product: [oVirt] cockpit-ovirt Reporter: Mugdha Soni <musoni>
Component: GdeployAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: Mugdha Soni <musoni>
Severity: low Docs Contact:
Priority: unspecified    
Version: 0.11.7CC: bshetty, bugs, rhs-bugs, sabose, sasundar
Target Milestone: ovirt-4.2.4Flags: sasundar: ovirt-4.2?
musoni: planning_ack?
rule-engine: devel_ack+
sasundar: testing_ack+
Target Release: 0.11.25   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.25-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1560413 Environment:
Last Closed: 2018-06-26 08:35:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1560413, 1582207    
Attachments:
Description Flags
screenshot of verification of the bug. none

Comment 2 Mugdha Soni 2018-06-20 07:40:52 UTC 
In reply to #comment1 (Mugsdha Soni)

The content for verification of the bug is inappropriate . The valid steps performed for testing this bug are given below :

Tested with the following:-
(1)Logged in to cockpit UI  and proceeded  gluster deployment.
(2)Configured the tabs hosts, fqdn, packages and volume .
(3)While configuring the tab bricks , under the configure lv cache ,user can sucessfully see the dropdown with two options i.e 'writeback' and write through'.

Hence moving this bug to verified state.
 
Raising a new bug as the writeback option in the dropdown is not accessible.
Comment 3 Mugdha Soni 2018-06-20 07:42:17 UTC 
Created attachment 1453133 [details]
screenshot of verification of the bug.
Comment 4 Sandro Bonazzola 2018-06-26 08:35:44 UTC 
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.