Description of problem: ----------------------- When the gluster deployment fails, cockpit UI throws the status in the text area and provides the option to redeploy. If chosen to redeploy, the generated gdeploy config file tab is shown, intending the user to make changes to the existing gdeploy conf file. At the same time, it allows the user to navigate to other tabs. If user changes the values, in those tabs, and comes back the generated gdeploy conf file tab, new gdeploy config file is not generated Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-0.10.9 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Provide the non-existing disk for bricks, say sdz and continue deployment from cockpit. Installation will fail, and cockpit provides option to 'Redeploy' 2. Go to the bricks tab, update the disk as 'sdb' 3. Navigate to the gdeploy conf file tab. Actual results: --------------- gdeploy conf file still contains the old data ( disk sdz ), which means the new gdeploy conf file is not generated post updating the disks in brick tab Expected results: ----------------- While choosing 'Redeploy', if the user corrects any of the input then new gdeploy config file should be generated
Tested with cockpit-ovirt-dashboard-0.11.23.el7 When redeployment is done, the gdeploy configuration files are regenerated according to the new changes
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