Deploy process frezzes with "Wait for the host to be up"
Hello everyone I'm installing ovirt 4.5 on a homelab VMWare Workstation (which I did several times weeks ago). Not so much that I'm going through technical problems. The deploy engine works in a stage called '[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]'. I couldn't find any error messages in both the Host logs and the Engine. Try different ways to automatically create the ovirtmgmt network, as you previously created it. The fact is that at this stage the engine is still not connected to the ovirtmgmt network, and from this point the depoloy does not pass through the host cannot communicate with the Engine with the FQDN informed.
Update ovirt-engine-appliance-almalinux9-4.5.7-20260118065914.1.el9.x86_64.rpm, solved the problem. Thank you to those involved.
Leandro, I ran into this with the latest installation script. From what I could tell, the oVirt Manager is trying to SSH back to the Host BEFORE it copies the public key from the VM to the authorized_keys file on the host. For me, this was after the vm was built, but before it was moved to the proper ovirtmgmt network. The VM was using the random IP assigned by the script. Here is how I bypassed this error. 1. During the question phase, I said "Yes" to the copy IP to /etc/hosts. 2. I opened a 2nd SSH session to the Host. Make sure you are at root on the 2nd session. 3. After the temp IP was assigned, I would SSH into the VM from the 2nd SSH Session. (I would normally cat /etc/hosts to see when the IP was listed there, but you can wait until yo see the "Wait for the host to be up" message.) You should be able to ssh as root the VM. 4. I think you can copy the host public key, but I just issued a ssh-keygen -t ed25519, and left the password blank. 5. I would then cat the .ssh/id_ed25519.pub file and copy the public key. 6. exit the ssh session to the vm. 7. copy the public key to .ssh/authorized_keys - Save and exit. At this time, the VM should be able to ssh back to the host and verifiy that the "host is up." Hope this helps.
I think for this to debug you will need to check the engine logs within the hosted engine VM. Those logs should give more information. On 16/01/2026 16:49, Leandro Pereira wrote:
Hello everyone
I'm installing ovirt 4.5 on a homelab VMWare Workstation (which I did several times weeks ago). Not so much that I'm going through technical problems.
The deploy engine works in a stage called '[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]'.
I couldn't find any error messages in both the Host logs and the Engine. Try different ways to automatically create the ovirtmgmt network, as you previously created it. The fact is that at this stage the engine is still not connected to the ovirtmgmt network, and from this point the depoloy does not pass through the host cannot communicate with the Engine with the FQDN informed. _______________________________________________ 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/VC6IEP3PHUT6G6...
I am also seeing similar issue where hosted engine installation stuck at "Wait for the host to be up". Nothing comes up in logs. I could see this before it is going into stuck mode but nothing it tells what to do next. Also while doing i saw vdsmd service goes down. Let the user connect to the bootstrap engine VM to manually fix host configuration'} 2026-02-16 17:11:50,695+0000 DEBUG ansible on_any args Let the user connect to the bootstrap engine VM to manually fix host configuration 'Let the user connect to the bootstrap engine VM to manually fix host configuration', 'ansible_host': 'localhost'}
Teilnehmer (4)
-
dushyantk.sun＠gmail.com -
Frank -
Jean-Louis Dupond -
Leandro Pereira