Dear Sandro, this gives me a clear idea of the status of the project unfortunately. But please let me explain my use case and maybe you can suggest me the correct solution. In my organization we have several ovirt installations, some with hosted engine, some with a separate VM running on "something else". Personally I have 2 instances that I care most and they are still running 4.5.4. You suggested several months ago that we should switch to nightlies, but since I need to be sure they work correctly, I want to test them on a separate tesbed. Hence I wanted to install a brand new mini cluster to test the nightlies before running them in production (I think this is the correct approach in general). Anyway since nightlies change quite often and are not versioned, it's not simple, I think, to test them on a testbed and then bring them in production, since some packages may have already been updated. So, what do yuo suggest me to do, to be sure I run in production only tested software? THanks a lot for your support. Andrea On 19/09/2023 16:43, Sandro Bonazzola wrote:

If this is a new install from scratch, I would recommend a CentOS Stream 9 based deployment and dedicate a host to the oVirt Engine or on a VM but not using a Hosted Engine.

Il giorno mar 19 set 2023 alle ore 16:30 Andrea Chierici <andrea.chierici@cnaf.infn.it> ha scritto:

Dear all, I've been struggling with a new ovirt installation for several weeks but I seem to have no luck at all. I've tried both starting from a centos8 stream system and a ovirt-node, but the engine installation always breaks here:

TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]

I keep getting the same problem, it looks like the engine is not "migrated" to the public ip and is stuck on the natted address that the installation process is using during the preliminary phase. Here is a message that seems to confirm my theory:

2023-09-19 15:43:29,259+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml':

line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n  ^ here\n", '_ansible_no_log': False} 2

I know the problem the development of ovirt is facing lately, but I am simply wondering: is there a way to install ovirt 4.5.4 today or is it all already lost??!

Any kind of help would be really appreciated. Thanks,

Andrea

-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

_______________________________________________ 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/RVZJNVRBK454LD...

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING

Red Hat In-Vehicle Operating System

Red Hat EMEA <https://www.redhat.com/>

<https://www.redhat.com/>

*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. * *

*

-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

Il giorno mar 19 set 2023 alle ore 17:03 Andrea Chierici < andrea.chierici@cnaf.infn.it> ha scritto:

Dear Sandro, this gives me a clear idea of the status of the project unfortunately. But please let me explain my use case and maybe you can suggest me the correct solution. In my organization we have several ovirt installations, some with hosted engine, some with a separate VM running on "something else". Personally I have 2 instances that I care most and they are still running 4.5.4. You suggested several months ago that we should switch to nightlies, but since I need to be sure they work correctly, I want to test them on a separate tesbed. Hence I wanted to install a brand new mini cluster to test the nightlies before running them in production (I think this is the correct approach in general). Anyway since nightlies change quite often and are not versioned, it's not simple, I think, to test them on a testbed and then bring them in production, since some packages may have already been updated. So, what do yuo suggest me to do, to be sure I run in production only tested software? THanks a lot for your support.

Andrea

Hi Andrea, oVirt project packages are tested only by the community these days, the same way you are testing them in your test bed. The suggestion to use nightly is still valid, it's the version which has the highest probability to really run on recent el8 and el9 streams / releases. If you need to snapshot a specific nightly I would suggest to take a local snapshot using foreman or just mirroring the repository and use it both for testing and for pushing to production after the test succeeds. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING Red Hat In-Vehicle Operating System Red Hat EMEA <https://www.redhat.com/> <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*