+++ This bug was initially created as a clone of Bug #1746451 +++ Description of problem: ------------------------ lvcache size should be the same as the one received from the user Version-Release number of selected component (if applicable): ------------------------------------------------------------- cockpit-ovirt-dashboard-0.13.36 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Enable lvcache 2. Input the size of lvcache Actual results: ----------------- Generated vars file has the lvcache size much lesser than the input one Expected results: ----------------- lvcache in generated vars file should be the same as input one Additional info:
I could see that this fix is part of cockpit-ovirt-dashboard-0.13.8 LV cache size from the input is reflected in the generated vars file @Sandro, Who is responsible for moving this bug to ON_QA so that it could be moved to verified
(In reply to SATHEESARAN from comment #1) > I could see that this fix is part of cockpit-ovirt-dashboard-0.13.8 > LV cache size from the input is reflected in the generated vars file > > @Sandro, > Who is responsible for moving this bug to ON_QA so that it could be moved to > verified I'm moving it to QA when a build including the fix is available in oVirt pre-release repos.
(In reply to Sandro Bonazzola from comment #2) > (In reply to SATHEESARAN from comment #1) > > I could see that this fix is part of cockpit-ovirt-dashboard-0.13.8 > > LV cache size from the input is reflected in the generated vars file > > > > @Sandro, > > Who is responsible for moving this bug to ON_QA so that it could be moved to > > verified > > I'm moving it to QA when a build including the fix is available in oVirt > pre-release repos. ok, thanks for the information
based on comment1, moving this bug to verified
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 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.