+++ This bug was initially created as a clone of Bug #1578686 +++ Description of problem: ---------------------------------------------- After there is a failure in the creation of the volume or expand cluster , it is not allowed to go back and edit the tab. The changes are not reflected in the config file . The user has to start configuring the tabs from the first i.e the host tab. Version-Release number of selected component (if applicable): --------------------------------------------- cockpit-ovirt-dashboard-0.11.23-1.el7ev.noarch How reproducible: ---------------------------------------------- Everytime Steps to Reproduce: --------------------------------------------- 1.Successfully deploy the gluster and hosted engine . 2.Click on the "Hosted Engine " tab and then " Manage gluster" tab in the cockpit UI. 3. Perform either of the functions from "create volume" and " add cluster". 4. If there is a failure then go to the previous tabs and change few parameters. Actual results: ----------------------------------------------- The edited parameters after the failure are not reflected in the config file. Expected results: ----------------------------------------------- THe edited parameters after the failure should be reflected in the conf file. --- Additional comment from Red Hat Bugzilla Rules Engine on 2018-05-16 03:34:30 EDT --- This bug is automatically being proposed for the current release of Red Hat Hyperconverged Infrastructure (RHHI) under active development, by setting the release flag 'rhhi‑2.0' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag.
Tested with the following: (a)rhvh-4.2.5.0-0.20180702.0+1 (b)cockpit-ovirt-dashboard-0.11.29-1.el7ev.noarch(3 (c)gdeploy-2.0.2-27.el7rhgs.noarch Any changes made after the failed deploy in the configuration of the tabs via cockpit UI is reflected in the conf file . Hence moving the bug to verified state.
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 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.