+++ This bug was initially created as a clone of Bug #1466132 +++ Description of problem: While running Hosted Engine with gluster as the deployment choice, the additional hosts are already known. Hosted engine deployment should continue to step to add the data domains and deploy additional hosts. Version-Release number of selected component (if applicable): 0.10.7 How reproducible: NA
*** Bug 1521135 has been marked as a duplicate of this bug. ***
*** Bug 1521123 has been marked as a duplicate of this bug. ***
@Sahina it appears that this bug is being used to track both adding hosts AND storage domains to hosted engine. (Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1521135 & https://bugzilla.redhat.com/show_bug.cgi?id=1521123) Is the plan to have all three hosts in the host tab and all three storage domains in the storage tab without any user intervention needed post RH-HI deployment? Just making sure that the heart of both bugs listed above isn't lost in the bug clone. Thanks, Dave PS. In regards to your comment on bug 1521135: "You should be creating the first Storage Domain with 'vmstore' volume as described in the doc ( chapter 9.2 in deployment guide ) If that is done, then the hosted-engine storage will be imported automagically. Let me know, if that doesn't work or doc is not clear to do the same." That is the procedure we've been following but the default cluster is deployed with the storage domain 'data' as well. Ideally all three storage domains should be imported without the need for user input. I haven't seen a lot of documentation about the 'data' storage domain and am curious how others are using that domain. We're planning on using all three domains in our testing.
Going through backlog. @Sahina I was wondering why the original bug (https://bugzilla.redhat.com/show_bug.cgi?id=1521135) was closed as a duplicate even though it was filed before this bug. Was it an attempt to consolidate bugs? Thanks, Dave
CSS Bug review: The CSS team is ok with this being implemented in the 2.0 release
This fix for this bug is broken with ansible-2.5.2 and this bug depends on 1574881 to be fixed
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
Could verify the bug in the latest cockpit-ovirt-dashboard-0.11.25-1. Adding the screeshot for the newly added FQDN wizard.
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
Added doc_text.
Hi Laura, I have just added SD info as well.It looks correct.
(In reply to Dave from comment #4) > Going through backlog. @Sahina I was wondering why the original bug > (https://bugzilla.redhat.com/show_bug.cgi?id=1521135) was closed as a > duplicate even though it was filed before this bug. Was it an attempt to > consolidate bugs? > Thanks, Dave Yes, since we filed this bug that includes the end to end flow and were tracking with a corresponding oVirt bug and acks, closed the previous one as duplicate as it is a subset of this.
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