[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-27 Thread thomas
Just fresh from a single node HCI setup (CentOS 8 + oVirt 4.4.1) I did yesterday on an Intel i7-8559U NUC with a single 1TB NVMe storage stick and 64GB of RAM: The HCI wizard pretty much assumes a "second disk", but a partition will actually do. And it doesn't even have to be in /dev/mapper, ev

[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-26 Thread Gianluca Cecchi
On Thu, Aug 27, 2020 at 2:49 AM David White via Users wrote: > > > The responses to the bugzilla make it sound like a second, unused, disk, > is required. Is that the case? > yes, it is required to install the OS from the ovirt-node-ng iso on the first disk and then select the second empty disk

[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-26 Thread David White via Users
Thanks. That helped me get past the FQDN issue. However, I'm now running into another problem that I think its related to this non-issue RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1833421 I'm attaching the ansible log to this email. (Is there a better way to provide log files?) The re

[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-26 Thread David White via Users
> I assume you follow: > > https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Single_node_hyperconverged.html > > It says you must configure passwordless ssh from the host to itself. > Did you do this? You gave me too much credit. My mistake. I did NOT setup passwordless ssh, and I al

[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-26 Thread Yedidyah Bar David
On Wed, Aug 26, 2020 at 2:32 AM David White via Users wrote: > > In a recent thread, Roberto mentioned seeing the error message "FQDN Not > Reachable" when trying to deploy oVirt Node 4.4.1, but was able to get past > that error when using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso. > > I