Bug 1584151
Summary: | [day2] Updated hosts are not persisted both the gdeploy config files | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Mugdha Soni <musoni> | |
Component: | rhhi | Assignee: | Sahina Bose <sabose> | |
Status: | CLOSED ERRATA | QA Contact: | Mugdha Soni <musoni> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhhiv-1.5 | CC: | godas, rhs-bugs, sankarshan, sasundar | |
Target Milestone: | --- | |||
Target Release: | RHHI-V 1.5 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | cockpit-ovirt-0.11.29-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1584152 (view as bug list) | Environment: | ||
Last Closed: | 2018-11-08 05:39:29 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1584152 | |||
Bug Blocks: | 1520836 |
Description
Mugdha Soni
2018-05-30 12:01:20 UTC
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 |