Description of problem: ----------------------------------------------------------- The change in any parameters required for expand cluster after the failed deployment is not reflected in the gdeploy conf file which is regenerated on redeploy because the change regarding the error is made in file "/var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf " and not in " /var/lib/ovirt-hosted-engine-setup/gdeploy/expandClusterConfig.conf '. Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-dashboard-0.11.999-0.0.master.el7.noarch How reproducible: -------------------------------------------------------------- Eerytime Steps to Reproduce: -------------------------------------------------------------- 1.Successfully deploy gluster and hosted engine. 2.Reach out to the gluster management wizard via hosted engine . 3.Click on ' expand cluster ' button , configure the paramneters and then deploy. Actual results: --------------------------------------------------------------- The change in parameter in any of the tabs is not reflected in the regenerated conf file after redeployment. Expected results: -------------------------------------------------------------------- The change in any of the parameter should be reflected in the regenerated gdeploy conf file. Additional info:- ------------------------------------------------------------------------ The changes should be made on both of these file rather than a single file. "/var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf " " /var/lib/ovirt-hosted-engine-setup/gdeploy/expandClusterConfig.conf '.
This issue is seen with expand cluster operation on the cockpit day2 operations. While trying to update the host names after passing the first tab ( take a case where the customer prefers to update the hostnames, or redeploying after failed attempt ), the new host names are persisted in the gdeploy config file used for configuring those hosts, but the other gdeploy file used for peer probing was not really updated and still refers to the old host lists
*** Bug 1584149 has been marked as a duplicate of this bug. ***
Tested with cockpit-ovirt-dashboard-0.11.30-1 with the following steps: 1. Proceed to 'Virtualization' tab -> 'HostedEngine' -> 'Gluster Management' -> 'Expand cluster' 2. New wizard pops-up, and provide the hostnames as 'host12', 'host13', 'host14' Note that this hostnames are not resolvable and doesn't exists. These hostnames are picked for the deployment to fail 3. Proceed with custom values for fields on other tab and proceed to deployment. 4. Once the deployment fails, click on 'Redeploy' and go back to the first tab and update the hostnames to 'host121', 'host131', 'host141' 5. Go to the last tab where you can see the generated gdeploy config file, but do not click on deployment. 6. Validate the gdeploy config files # grep -A4 hosts /var/lib/ovirt-hosted-engine-setup/gdeploy/expandClusterConfig.conf # grep -A3 hosts /var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf The list contains the updated hosts
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