+++ This bug was initially created as a clone of Bug #1704183 +++ See https://bugzilla.redhat.com/show_bug.cgi?id=1659052 for details on the option. --- Additional comment from Wei Wang on 2019-05-05 07:44:56 UTC --- According to https://github.com/oVirt/ovirt-site/blob/529f45a80942556d1ee62cef674df48fa38ce60d/source/develop/release-management/features/sla/hosted-engine-network-check.html.md QE change the testing_ack to "+"
Test Version RHVH-4.3-20190516.1-RHVH-x86_64-dvd1.iso cockpit-ovirt-dashboard-0.12.9-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.8-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch Test Steps: 1. Clean install RHVH-4.3-20190516.1-RHVH-x86_64-dvd1.iso 2. Open cockpit web UI : http://localhost:9090 3. Start the hosted-engine wizard 4. Set "Network Test" to DNS/ping/TCP/None in engine vm setting. 5. Deploy hosted engine Result: 1. Hosted engine deploy successfully 2. Three parameters network_test, tcp_t_address, tcp_t_port in hosted-engine.conf have set rightly. Bug is fixed, change the status to "VERIFIED"
Please check new doc text: Previously, you could only test a host's network connectivity with ICMP (ping). Sometimes the gateway does not reply to a ping request, such as when ping is blocked at the network level. When such a failure occurred during the installation of a self-hosted engine, the installation failed. Now you can test network connectivity by checking if the DNS resolution is working, by pinging the gateway, by testing a TCP connection to a configurable port on a configurable host, or you can proceed with installation without running any test
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:1560