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.
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.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3523