Bug 1466132
Summary: | [HC] when running hyperconverged deploy, the 2nd and 3rd host should be auto added | |||
---|---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Sahina Bose <sabose> | |
Component: | Plugins.Gluster | Assignee: | Gobinda Das <godas> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 2.2.0 | CC: | bshetty, bugs, cshao, dfediuck, sasundar, seamurph, stirabos, ylavi | |
Target Milestone: | ovirt-4.2.5 | Keywords: | FutureFeature | |
Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
ylavi: planning_ack+ sabose: devel_ack+ sasundar: testing_ack+ |
|
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | ovirt-hosted-engine-setup-2.2.19-1.el7ev | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1523568 (view as bug list) | Environment: | ||
Last Closed: | 2018-07-31 15:30:39 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1470571, 1574881 | |||
Bug Blocks: | 1458709, 1523568 |
Description
Sahina Bose
2017-06-29 06:55:54 UTC
The fix failed with the latest ansible-2.5.2 This bug depends on the fix for the bug 1574881 and blocked on verification Tested with RHV 4.2.3-6 and RHHI 1.1, and HE deployment failed, as the 2nd and 3rd nodes were tried to be added to RHV using the backend IP, and the engine fails to ping the backend IP, as it falls in to different subnet Tested on ovirt-hosted-engine-setup-2.2.22-1.el7ev.noarch. Moving to fixed. With the latest RHV-4.2.4-3 build, while adding the 2 hosts while doing RHHI deployment, failed to add the host automagically to the cluster This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 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. |