[ovirt-users] Re: The he_fqdn proposed for the engine VM resolves on this host - error?

On Thu, Jan 28, 2021 at 5:12 PM lejeczek via Users <users(a)ovirt.org <mailto:users@ovirt.org>> wrote: On 28/01/2021 13:42, Yedidyah Bar David wrote: > On Thu, Jan 28, 2021 at 3:26 PM lejeczek via Users <users(a)ovirt.org <mailto:users@ovirt.org>> wrote: >> >> >> On 28/12/2020 21:21, Edward Berger wrote: >>> The hosted engine fqdn and IP address should be separate >>> from the hypervisor host's IP address but on the same >>> network so it can communicate to the host through a >>> bridged interface that the installer creates on the >>> hypervisor host for the hosted engine VM. >>> >>> On Mon, Dec 28, 2020 at 3:14 PM lejeczek via Users >>> <users(a)ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> wrote: >>> >>>      hi chaps, >>> >>>      a newcomer here. I use cockpit to deploy hosted engine >>>      and I >>>      get this error/warning message: >>> >>>      "The he_fqdn proposed for the engine VM resolves on >>>      this host" >>> >>>      I should mention that if I remove the IP to which FQDN >>>      resolves off that iface(plain eth no vlans) then I get >>>      this: >>> >>>      [ ERROR ] fatal: [localhost]: FAILED! => {"changed": >>>      false, >>>      "msg": "The selected network interface is not valid"} >>> >>>      All these errors seem bit too cryptic to me. >>>      Could you shed bit light on what is oVirt saying >>>      exactly and >>>      why it's not happy that way? >>> >>>      many thanks, L. >>> _______________________________________________ >>>      Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> >>>      <mailto:users@ovirt.org <mailto:users@ovirt.org>> >>>      To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> >>>      <mailto:users-leave@ovirt.org <mailto:users-leave@ovirt.org>> >>>      Privacy Statement: >>> https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> >>>      <https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html>> >>>      oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> >>>      <https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/>> >>>      List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LTAYI3GYI2A... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/LTAYI3GYI2A... >>>      <https://lists.ovirt.org/archives/list/users@ovirt.org/message/LTAYI3GYI2A... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/LTAYI3GYI2A... >>> >> When I played a bit with it now I get a different failure: >> ... >> [ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check the >> resolved address resolves on the selected interface] >> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, >> "msg": "The resolved address doesn't resolve on the selected >> interface\n"} >> ... >> >> Is this the hosted-engine address installer complains about? >> Before I go further down the rabbit hole - can deployment be >> done solely with "hosts" and no DNS? > In principle, it can, and if it can't, that's a bug - please report one. > > I didn't try that myself recently. > > Please note that if you rely on /etc/hosts, the deploy process can "help" > you with this (see the relevant questions it asks), but it's still up to > you to make sure the information is correct (which is true, btw, also with > dns). > > For your specific error above, please check the logs - you should find > "he_host_ip" there and see if it's correct. > > Best regards, Gee, to a novice such a myself this is off-putting disaster rather than nice intro to oVirt. Sorry for that.

It fails for me with or without DNS. Sure I fail to grasp the concepts here but docs is the place where I got to first and cannot find there anything which would nicely explain the meaning of network config prior to "hosted engine" deployment. Sure my config is not the most basic but neither it is very complex yet I can run circles with how oVirt employment, at the moment, endlessly. I have three subnets, a) I'd like to keep as external Probably not directly related to your issue, but please explain what this means. No host is connected there, and the engine VM should not access it? Or hosts _are_ connected, and you intend other VMs to be able to connect there, but not the engine vm? Or something else? b) would be oVirt "oVirt" is not just a single kind of application/communication. People sometimes use separate networks for console access, for VM migrations, etc. c) I'd like to keep internal but away from oVirt, for purposes like storage OK. so.. I take of host name resolution (hosts or dns or both together) and start deployment in shell console. .. 1) first is the gateway which "hosted-engine" proposes to be a gateway on "external" net. Which I ignore as that would not work with what I want later down the process - "b" network to be used by oVirt - and I tell it so use 10.5.8.254 (which is not a real gateway as it does not route to the "outside") I think this shouldn't be a problem (but didn't check recently). 2) I tell it to use "enp34s0f0np0" iface (that is host's iface which already has 10.5.8.49 on it). Other ifaces installer proposes are not good (obviously I do not want iface which is on "external" subnet). I assume it's the one connected to your (b) network, right? For "network connectivity" I've tried ping & dns. 3) Engine VM FQDN:  []: buster.private.ccn. (that resolves to 10.5.8.1 via hosts/dns and that is that the same "b" for oVirt net. This IP is not assigned to any iface, as I understand - it should not be) Correct. 4) Then I choose:   VM network be configured? (DHCP, Static)[DHCP]: static   Please enter the IP address to be used for the engine VM []: 10.5.8.1 5) I tell it to use three DNSes (I'm aiming at 3-node cluster) on the same "b" subnet: 10.5.8.49,10.5.8.65,10.5.8.97 Not sure what you mean here. I assume these addresses are of your local name servers, right? And the fact you have/use 3 is for redundancy of the dns service. It's not related to the redundancy of the oVirt hosts. 6) For management: Please provide the hostname of this host on the management network - I say use "whale.private.ccnr.away", which is "c" subnet. Why c? I thought you want b for "oVirt". And eventually I hit: ... [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The resolved address doesn't resolve on the selected interface\n"} It's hard to understand just this error, but if you check the log you should see around that what it tried to match and failed. The ansible code doing this is (on your host) in: /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/002_validate_hostname_tasks.yml         - name: Check the resolved address resolves on the selected interface           fail:             msg: >               The resolved address doesn't resolve               on the selected interface           when: >-             he_host_ip not in target_address_v4.stdout_lines and             he_host_ip not in target_address_v6.stdout_lines You should be able to find the values of the used variables earlier in the log. ... and a few lines later (which probably matter less if at all): ... [ ERROR ] fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host buster.private.ccn. port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true} Likely. But it can definitely be due to the same root cause. .. I read post on the net, those I found, say "easy", but my initial experience is the opposite, it's like I mentioned - off-putting. Again sorry for that. Would anybody have a pointer I could follow where "network" part of deployment is nicely and precisely covered? I admit I didn't read recently the installation docs so not sure that's covered in detail. There is this RHV document, which should apply more-or-less 100% to oVirt, but not sure it would help you with your concrete issue: https://www.redhat.com/en/resources/best-practice-rhv-technology-detail <https://www.redhat.com/en/resources/best-practice-rhv-technology-detail> Or any suggestions with what I'm missing here? I think the issue is perhaps using the wrong nic/network. Good luck and best regards, -- Didi