Question 1: In General, can i install oVirt Node and hosted-engine on
one physical server?
Yes and single node hyperconverged is suggested for single node deployments.
Question 2: What domain names should I specify in the DNS server and
which ones IP should I reserve?
You can use any domain name you have ownership of and control the DNS for,
as seen to and from your host and VMs
not localhost.
You want two hostnames that resolve to the same network/netmask, one for
the hypervisor, one for the engine VM.
The installer will create a network bridge for the engine VM off the host's
ethernet which the two will communicate over
and it will be available for any other VMs you deploy later with that
network..
This network must be reachable via your web browser, so it is usually a
public network address,
For updates, installation needs, etc. both host and engine will want to
reach out to the internet.
If you're planning on adding more storage servers, another network as a
private network and hostname that
resolves to it would be suggested, but it isn't necessary in the single
host case.
Question 3: "Failed to connect to the host via ssh: ssh: connect
to host
ovirt-engine-01.local port 22: No route to host" - Who and where is
trying
to establish a connection via SSH?
The host will try to ssh to the engine VM and the engine VM will will try
to communicate to the host.
The main accounts are root and vdsm. I'm not sure of others.
On Sun, Mar 7, 2021 at 2:17 AM <ivanpashchuk(a)ipoft.com> wrote:
> oVirt node 4.4.4
>
> Question 1: In General, can i install oVirt Node and hosted-engine on one
> physical server?
>
> Question 2: What domain names should I specify in the DNS server and which
> ones IP should I reserve?
>
Question 3: "Failed to connect to the host via ssh: ssh: connect
to host
> ovirt-engine-01.local port 22: No route to host" - Who and where
is trying
> to establish a connection via SSH?
>
> Can someone reply to questions 1-3 above? Any help will be much
> appreciated.
>
> Thanks for the help,
> Ivan.
>
> Logs:
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"attempts": 180, "changed": true, "cmd":
["hosted-engine", "--vm-status",
> "--json"], "delta": "0:00:00.565239", "end":
"2021-03-03 13:36:54.775239",
> "rc": 0, "start": "2021-03-03 13:36:54.210000",
"stderr": "",
> "stderr_lines": [], "stdout": "{\"1\":
{\"host-id\": 1, \"host-ts\": 16377,
> \"score\": 3400, \"engine-status\": {\"vm\":
\"up\", \"health\": \"bad\",
> \"detail\": \"Up\", \"reason\": \"failed
liveliness check\"}, \"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false,
\"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\":
true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar 3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar 3
> 13:36:48
>
2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=
> False\\n\", \"live-data\": true}, \"global_maintenance\":
false}",
> "stdout_lines": ["{\"1\": {\"host-id\": 1,
\"host-ts\": 16377, \"score\":
> 3400, \"engine-status\": {\"vm\": \"up\",
\"health\": \"bad\", \"detail\":
> \"Up\", \"reason\": \"failed liveliness check\"},
\"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false,
\"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\":
true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar 3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar 3
> 13:36:48
>
2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"live-data\": true}, \"global_maintenance\": false}"]}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"changed": false, "msg": "Engine VM IP address is while
the engine's
> he_fqdn ovirt-engine-01.local resolves to 10.0.2.250. If you are using
> DHCP, check your DHCP reservation configuration"}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! =>
> {"changed": false, "msg": "Failed to connect to the host via
ssh: ssh:
> connect to host ovirt-engine-01.local port 22: No route to host",
> "skip_reason": "Host localhost is unreachable",
"unreachable": true}
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLNLHUJLKQ4...
>