Previously, during deployment of an additional self-hosted engine node, the Manager was expecting a configuration archive of 20480 bytes; but in certain circumstances, the size of the configuration archive was just 10240 bytes. This caused the deployment to fail. Now the block size is forced at tar level to avoid such failures, and a file size check has been added.
+++ This bug is a downstream clone. The original bug is: +++
+++ bug 1480039 +++
======================================================================
Description of problem:
Additional HE host deploy fails and doesn't get deployed as HE, but normal host
Version-Release number of selected component (if applicable):
rhevm-4.1.3.5-0.1.el7.noarch
How reproducible:
100% in customer's environment
Steps to Reproduce:
1. Place host into maintenance
2. Installation > Reinstall > Hosted Engine > Undeploy
3. Installation > Reinstall > Hosted Engine > Deploy
Or
1. Add a new host > Hosted Engine > Deploy
Actual results:
HE host is being installed as regular host
Expected results:
Host installed as part of the HE cluster
Additional info:
(Originally by Javier Coscia)
Works for me on cleanly deployed ovirt-hosted-engine-setup-2.1.4-1.el7ev.noarch with rhvm-appliance-4.1.20170914.0-1.el7.noarch and ovirt-engine-setup-4.1.6.2-0.1.el7.noarch inside on pair of RHEL7.4 hosts.
See also attached screencast.
Moving to verified.
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/RHBA-2017:3136
Comment 14Simone Tiraboschi
2018-08-24 09:42:21 UTC
*** Bug 1613278 has been marked as a duplicate of this bug. ***