Red Hat Bugzilla – 1679797 – deployment is trying reach 1st host instead of HE FQDN with error: Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>,
deployment is trying reach 1st host instead of HE FQDN with error: Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>,
I faced the very same issue according to Simone, while I was trying to restore from the backup, e.g. "hosted-engine --deploy --restore-from-file=nsednev_from_alma03SPM_rhevm_4_3".
The issue was fixed in ovirt-ansible-engine-setup-1.1.8-1.el7ev, so after retrying the same restore procedure, this bug was fixed and verified.
ovirt-ansible-engine-setup-1.1.8-1.el7ev.noarch
rhvm-appliance-4.3-20190220.2.el7.x86_64
ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)
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/RHEA-2019:1064