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

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, even if the wizard seems to have some logic requiring that. But it requires a partition to be present, which you'll need to create (empty) by hand and which in my case was something like /dev/nvme0n1p10 where the wizard puts /dev/sdb. That's because the wizard will then try to put VDO on that storage, which requires a block layer underneath, and then puts thin allocation LVs on to of that for the ultimate flexibility and the ability to worry much more about performance than detail planning of storage allocations. And it needs to be really empty, if there is a file system or left-overs of one, the Wizard will fail with a not very helpful "device xx has been blacklisted" or similar. Of course, without the HCI (first choice you make in the Wizard), you can set up your storage, even with Gluster, in many other ways, but I've found it easier to stick with the HCI route, at least given the equipment I had (no SAN, no NFS filer).