On 11/05/2023 18:18, Volenbovskyi, Konstantin wrote:
Hi,
Is it actually first attempt to install HE? Or maybe you ran into some (different) problem and this is like second (third, fourth…) attempt.
While installation script takes care of some cleanup, I would say that you should consider doing
ovirt-hosted-engine-cleanup
,checking that virbr0 is absent in ‘ip a’ output
and trying once again
BR,
Konstantin
*Von: *lejeczek via Users <users@ovirt.org> *Antworten an: *lejeczek <peljasz@yahoo.co.uk> *Datum: *Donnerstag, 11. Mai 2023 um 13:25 *An: *"users@ovirt.org" <users@ovirt.org> *Betreff: *[ovirt-users] engine setup fails: error creating bridge interface virbr0: File exists - ?
Hi guys.
I'm trying to setup the engine on the latest stable ovirt node(in a VM), so a clean, vanilla-default system.
-> $ hosted-engine --deploy --4 ... [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Activate default libvirt network] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-start", "default"], "delta": "0:00:00.042134", "end": "2023-05-11 11:08:59.248405", "msg": "non-zero return code", "rc": 1, "start": "2023-05-11 11:08:59.206271", "stderr": "error: Failed to start network default\nerror: error creating bridge interface virbr0: File exists", "stderr_lines": ["error: Failed to start network default", "error: error creating bridge interface virbr0: File exists"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed getting local_vm_dir ...
Any & all suggestions on how to fix/troubleshoot this are much appreciated. many thanks, L.
No, it is a clean install of oVirt node in a KVM guest/VM. All I do in the node is I configure two ifaces and both are "regular" ethernets, then I start HE setup. Bare-metal host is Centos 9 Stream with everything up-to-dayte off the distro repos. I'd think this should be easily reproducible. ps. please keep replies to the bottom - this is not a conversion between two of us nor any two persons, Mailing to list - think of it a book, which always reads top-to-bottom. many thanks, L.