+++ This bug was initially created as a clone of Bug #1521215 +++ 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
Hi SAS, I am not able to reproduce in my dev environment which is master code base. Steps followed: 1- Leave all values as defult with wrong hosts,then deployment fails. ex. device: sdb 2- Clicked "Redeploy" -> Back (Brick wizard) -> changed device to "sdd" and changed size also -> Next -> gdeploy.conf file generated with "sdd" entries and given size as well.
(In reply to Gobinda Das from comment #1) > Hi SAS, > I am not able to reproduce in my dev environment which is master code base. > > Steps followed: > 1- Leave all values as defult with wrong hosts,then deployment fails. > ex. device: sdb > > 2- Clicked "Redeploy" -> Back (Brick wizard) -> changed device to "sdd" and > changed size also -> Next -> > gdeploy.conf file generated with "sdd" entries and given size as well. Gobinda, The issue is found with latest cockpit-ovirt-dashboard available in RHV 4.1.8 If the issue now not found in master, then there should be some patch that should have fixed it. Please move this to bug to ON_QA with the latest available cockpit-ovirt-dashboard as fixed-in-version QE will verify this bug for 4.1.9 or 4.2, based on where the fix has landed.
As per comment#1, this issue is **not** found with master, and Gobinda was unable to find the patch that solved the issue. I will retest the issue with cockpit-ovirt-dashboard available with RHV 4.1.9. If this issue is not found, then this bug could be targeted for RHV 4.1.9 and moved ON_QA
(In reply to SATHEESARAN from comment #3) > As per comment#1, this issue is **not** found with master, and Gobinda was > unable to find the patch that solved the issue. > > I will retest the issue with cockpit-ovirt-dashboard available with RHV > 4.1.9. > If this issue is not found, then this bug could be targeted for RHV 4.1.9 > and moved ON_QA Tested with RHV 4.1.9, and this issue is not observed. After clicking 'Redeploy' user could edit the values which gets reflected in the generated gdeploy config file. So this problem is fixed in RHV 4.1.9 as mentioned in comment3 Sahina, Could you move this bug to ON_QA, with release version set to RHV 4.1.9, so that it could be verified ?
As mentioned in comment4, this issue is not seen with cockpit-ovirt-dasboard-0.10.10 with RHV 4.1.9
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.