Created attachment 1523072 [details] the configuration of parameters as per requirement. +++ This bug was initially created as a clone of Bug #1669106 +++ Description of problem: ------------------------- Gdeploy config file in RHEL based RHHI deployment is not correct.It has all the defaults parameter except the hosts section.Even in " /var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf " the only change that is reflected are the hosts. Version-Release number of selected component: ---------------------------------------------- Red Hat Enterprise Linux Server release 7.6 (Maipo) cockpit-ovirt-dashboard-0.11.38-1.el7ev glusterfs-server-3.12.2-32.el7rhgs How reproducible: ----------------------- Everytime Steps to Reproduce: ----------------------- 1.Log in to the cockpit UI and edit the parameters required for gluster deployment. 2.Reach out to review tab and user can see that the changes are not reflected. 3.Go to the cli and run command " vi /var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf " the changes are not reflected here . Actual results: ----------------------- Gdeploy is not generate as per requirement Expected results: ----------------------- Gdeploy should generate as per requirement. --- Additional comment from Mugdha Soni on 2019-01-24 11:10 UTC ---
Created attachment 1523073 [details] gdeploy conf file
Can you check?
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Fixed and patch merged.
4.2.8 is handled in bug #1677662, re-targeting this to 4.3.1
Tested with the following 1. RHV 4.2.8 2. cockpit-ovirt-dashboard-0.11.39-1.el7ev The changes made in all the tabs during gluster deployment are reflected in gdeploy config file in review tab and in location " /var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf" Hence , moving the bug to verified.
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 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.