Let me try and break this down into a sequence of steps and let's see where it breaks down for you. Let's start with the simplest scenario. Centos 9 Stream system (6 core, 32Gb memory, 250Gb disk, single 1GbE nic - note i'm doing this in a virt-enabled VM, but bare metal should be similar). This is the sort of information I need to debug your problem.

Build a vanilla Centos 9 Stream system. (non-oVirt node image, but we can do that if you like)
My centos 9 system is called ovnode01.<fqdn> 192.168.1.111 and the manager i'm going to install is emanager.<fqdn> 192.168.1.251, both fqdn's resolve in my DNS (important)
As per https://ovirt.org/download/install_on_rhel.html

cat >/etc/yum.repos.d/CentOS-Stream-Extras-common.repo <<'EOF'
[c9s-extras-common]
name=CentOS Stream $releasever - Extras packages
metalink=https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-$stream&arch=$basearch&protocol=https,http
gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Extras
gpgcheck=1
repo_gpgcheck=0
metadata_expire=6h
countme=1
enabled=1
EOF

echo "9-stream" > /etc/yum/vars/stream

dnf distro-sync --nobest

dnf copr enable -y ovirt/ovirt-master-snapshot centos-stream-9
dnf install -y ovirt-release-master

You should get something like this
Running transaction

Preparing : 1/1

Installing : tar-2:1.34-7.el9.x86_64 1/2

Installing : ovirt-release-master-4.5.6-0.0.master.20240719070214.gitf7ad2c3.el9.noarch 2/2

Running scriptlet: ovirt-release-master-4.5.6-0.0.master.20240719070214.gitf7ad2c3.el9.noarch 2/2

Verifying : ovirt-release-master-4.5.6-0.0.master.20240719070214.gitf7ad2c3.el9.noarch 1/2

Verifying : tar-2:1.34-7.el9.x86_64

```
dnf install ovirt-hosted-engine-setup
```
Apart from this message 'Repository copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot is listed more than once in the configuration' you should have no other repository issues at this time.
663 packages later..... (my initial builds are minimal installs)
Remembering the above comment about the dns resolution of this node and the about to be built manager vm - make sure the dns resolves correctly to the systems you're about to build.
hosted-engine --deploy --4
Pretty much hit enter for most things, except for the following:

Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]:ping
Engine VM FQDN:emanager.<fqdn>
Enter root password that will be used for the engine appliance:<your password>
How should the engine VM network be configured? (DHCP, Static)[DHCP]:Static
Please enter the IP address to be used for the engine VM []:192.168.1.251 # the ip address emanager.<fqdn> resolves to.
Enter engine admin password:<your password>
Please provide the hostname of this host on the management network [ovnode01]:ovnode01.<fqdn> # fully qualified name that we know resolves to the correct ip address.
....... Lots of stuff happens
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Install oVirt Hosted Engine packages]
[ INFO ] ok: [localhost]
...
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Install ovirt-engine-appliance rpm] (sits here for quite a while as the rpm contains the appliance vm, it has to install the rpm, unwind it, copy bits and pieces around etc)

Eventually you'll get to

Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]:nfs
Please specify the nfs version you would like to use (auto, v3, v4, v4_0, v4_1, v4_2)[auto]:
Please specify the full shared storage connection path to use (example: host:/path):192.168.1.250:/ovirtx
If needed, specify additional mount options for the connection to the hosted-engine storagedomain
(example: rsize=32768,wsize=32768) []:

...

Please specify the size of the VM disk in GiB: [51]:

Building engine vm and shoving it out on NFS (In my case)

...

[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Shutdown local VM]

[ INFO ] changed: [localhost]

[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for local VM shutdown]

...

TASK [ovirt.ovirt.hosted_engine_setup : Copy local VM disk to shared storage]

...

[ INFO ] Stage: Pre-termination

[ INFO ] Stage: Termination

[ INFO ] Hosted Engine successfully deployed

And hey presto the manager should be at https://emanager.<fqdn>

From: Marco Fiorletta
Sent: Monday, March 03, 2025 7:00 PM
To: Geoff O'Callaghan; users@ovirt.org
Subject: Re: [ovirt-users] Re: Couldn't resolve host name for http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=storage-ceph-pacific

Hey there, I've been running into a really frustrating issue while trying to set up a self-hosted engine. I've tried multiple times, with different distributions like CentOS Stream 9, AlmaLinux 9.5, and Rocky Linux 9, but I keep hitting the same wall.

Essentially, during the engine configuration, I get an error saying that https://mirroros.centos.org is unreachable.

I've tried all the repository workarounds I've seen online, changing the pointers and everything, but nothing seems to help.

The weird thing is, if I install the engine on a dedicated server, it works fine. It's only when I try to deploy a self-hosted engine that I get this mirror error.

Then, just to see what would happen, I gave Oracle Linux a shot. And guess what?

The self-hosted engine configured perfectly, without even trying to touch those CentOS repositories.

So, that's definitely pointing to some kind of distribution-specific issue.

On top of that, I've also run into another problem with the 4.5 distribution related to VLANs.

I'm working in a data center with a bunch of VLAN-certified networks.

I wanted to set up oVirt 4.5, using a self-hosted engine, and assign one of those VLAN networks to ovirtmgmt.

But the installation just flat-out fails because it only seems to accept physical network devices.

The only way I could get it to work was to put a switch in place to mask the VLAN, which is a bit of a clunky workaround.

My older 4.4-based virtualizer didn't have any of these problems, so I'm wondering if something's changed significantly in 4.5. Any ideas?

Best regards

On Sun, 2025-03-02 at 20:56 +0000, Geoff O'Callaghan wrote:

Hi

I'm not sure where things are going wrong for you, so I built a new Centos 9 Stream system and was able to install a self-hosted appliance on it - ie. It got turned into a node and the engine appliance was deployed OK. I just wanted to make sure the current process worked.

Can you provide more information on what/how you're doing the installation? It might be that the documentation is wrong, but I will fix it if you can tell me where you're going wrong.

Thanks

Geoff

From: fiorletta--- via Users
Sent: Tuesday, February 25, 2025 3:30 AM
To: users@ovirt.org
Subject: [ovirt-users] Re: Couldn't resolve host name for http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=storage-ceph-pacific

I have the same problem.
Centos stream 9, ovirt 4.5 the errore is present only on self-hosted-engine.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/5TXJXB5FCV35PLXWKRZCYG3B75BBA3HU/

--