On Wed, Jan 25, 2023 at 13:17, lars.stolpe@bvg.de
<lars.stolpe@bvg.de> wrote:
Hi,
i'm planing to upgrade our production environment from oVirt 4.3 to 4.4.
So i do need a fresh oVirt 4.3 installation to test the procedure before doing it in production.
The command line deploy script can't handle network interfaces correctly. If i use either a single NIC oder a bond (active/passive) i get the error message "The selected network interface is not valid".
If i predefine the management bridge to a running state, the deploy process goes on, but fails to activate the added host and removes the already running engine vm.
The deploy process fails to synchronize the existing working network configuration with the engine configuration.
I can already log in to the engine GUI and see, that the bridge "ovirtmgmt" needs to be assigned to the bonding IF, but i'm not fast enough to do so, because the deployment process ist already shutting down and erasing the vm.
I do see the following ways to succeed:
1. make the depoyment process accept the given interfaces (maybe ignore errors)
2. make the deploy process wait for me to take necessary actions before checking the engine
Do anyone know, how to achieve this?
All i need is a running engine on hosted_storage... any other issues i can fix later.
Another idea is to use one of the destined hosts as a bare metal engine, add hosts, backup the engine and use that backup for a hosted engine restore deploy, since the deploy script asks to wait after local vm is ready, but only if i do a recovery deploy.
Any suggestions?
_______________________________________________