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

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 responses to the bugzilla make it sound like a second, unused, disk, is required. Is that the case? Reviewing https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Single_no..., I don't see any mention about a separate disk device being a requirement. For purposes of my testing, I was simply expecting the installer to create new directories in the root of the existing server. I tried manually creating the paths, but that didn't work either: [root@dev1-centos gluster_bricks]# mkdir -p /gluster_bricks/engine/engine [root@dev1-centos gluster_bricks]# mkdir -p /gluster_bricks/data/data [root@dev1-centos gluster_bricks]# mkdir -p /gluster_bricks/vmstore/vmstore I have two hard drives in this server, but they are currently in a RAID. For testing purposes, do I need to destroy the RAID, install onto 1 drive, and use the 2nd drive for the data? And is this basically what I should expect for a 3-node deployment as well? Make sure I have two different devices, 1 for the host OS and 1 for the data? Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, August 26, 2020 5:41 AM, David White via Users <users(a)ovirt.org&gt; wrote: > >