Description of problem:
with the current version of cockpit-ovirt-gdeploy plugin, when ever deployment fails user has to provide all the inputs again for re-deployment. Provide an easy way for the user to roll back in case deployment fails, i.e may be provide an option for the user to reload the same config file and provide a redeploy buton or provide a back button kind of thing where he can go to the "Review" page again and do the deployment by changing some parameters.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install latest cockpit-ovirt
2. Login to the UI
3. Provide all the inputs and give some wrong password so that deployment fails.
Once user clicks on back button it shows the Brick creation page and user has to re provide all his inputs.
provide an easy way for the user to roll back in case deployment fails.
Bug - 1415984 - is tracked for saving the gdeploy conf file under persistent location ( for example: /var/log/vdsm/ ) and each gdeploy conf file generation should have a unique file name by associating filename with timestamp.
This bug should provide UI enhancements to use the existing gdeploy conf file
We can provide a Redeploy option when deployment fails. User can use this option to see the review page again and he can also move back to previous steps and edit the configurations/inputs as required and Deploy again. This feature also can be used to implement the preflight checks (bz#1423542) in gdeploy. If preflight checks fails then user will get an option to edit the configuration and re-deploy.
In the case of failure, cockpit wizard lands up the final gdeploy config file display tab, where the user could edit the config file and redeploy
(In reply to SATHEESARAN from comment #3)
> In the case of failure, cockpit wizard lands up the final gdeploy config
> file display tab, where the user could edit the config file and redeploy
Tested with cockpit-ovirt-dashboard-0.10.7-0.0.11