Description of problem:
Forth to our conversation with Simone, I'm opening this bug due to failed addition of ha-host to SHE environment, deployed using --ansible, over Gluster storage.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Deploy SHE over gluster storage.
2.Don't add additional storage domains.
3.Add additional ha-host using UI.
Host being added, but as regular host only, instead of being added as ha-host.
Host shown without crown symbol and in CLI shown as "alma03 ~]# hosted-engine --vm-status
You must run deploy first"
Host should be added as ha-host, once chosen as such during addition process.
Sosreports from all hosts and engine attached.
Created attachment 1359474 [details]
logs from failed host alma03
Created attachment 1359475 [details]
logs from alma04
Created attachment 1359488 [details]
logs from the engine
Created attachment 1359490 [details]
hostdeploy logs from engine
This is not a regression! Node 0 way of deployment was never released yet, the old flow still works well I presume. Meaning this is "just" a bug in RFE for as long as Node 0 is not the default deployment method for 4.2.0 (which it is not).
Please do not link Node 0 issues to general hosted engine bugs that have nothing to do with deployment.
Dropping regression keyword and blocker flag according to comment #5
This is not a regression although it might very well be a blocker as we want to have Node 0 in (as alternative) for testing.
Works fine on clean --ansible SHE deployment over RHEL7.4, using ovirt-hosted-engine-setup-2.2.1-0.0.master.20171206172737.gitd3001c8.el7.centos.noarch and ovirt-engine-appliance-4.2-20171210.1.el7.centos.noarch.
Moving to verified.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.