[ovirt-users] oVirt 4.5.2 - ovirt-hosted-engine-setup fails with "error: Must be number, not str"}]" when creating ovirtmgmt network

2022-09-05 Thread Thomas Simmons
Hello, I am trying to deploy the latest oVirt (4.5.2), on a fully patched Rocky 8.6 system and am having and issue where "ovirt-hosted-engine-setup" is failing when it tries to create the ovirtmgmt network with the error "error: Must be number, not str"}]". When this happens, the engine setup

[ovirt-users] Re: VMs hang periodically: gluster problem?

2022-09-05 Thread Diego Ercolani
I don't have disk problems as I enabled smartd and I perform a periodic test (smartctl -t long ) but in sanlock I have some problems, and also in gluster glheal logs are not clean: The last event I recorded is today at 00:28 (22/09/4 22:28 GMTZ), this is the time when node3 sent mail:

[ovirt-users] Re: hosted-engine -vm-status show a ghost node that is not anymore in the cluster: how to remove?

2022-09-05 Thread Diego Ercolani
Perfect! It works Thank you Sandro. The help file is discouraging the use: [root@ovirt-node3 ~]# hosted-engine --clean-metadata --help Usage: /usr/sbin/hosted-engine --clean_metadata [--force-cleanup] [--host-id=] Remove host's metadata from the global status database. Available only in

[ovirt-users] Re: hosted-engine -vm-status show a ghost node that is not anymore in the cluster: how to remove?

2022-09-05 Thread Sandro Bonazzola
Il giorno lun 5 set 2022 alle ore 07:59 Sandro Bonazzola < sbona...@redhat.com> ha scritto: > > > Il giorno ven 2 set 2022 alle ore 17:26 Diego Ercolani < > diego.ercol...@ssis.sm> ha scritto: > >> Anyone can give a hint please? >> > > You can use the procedure at

[ovirt-users] Re: hosted-engine -vm-status show a ghost node that is not anymore in the cluster: how to remove?

2022-09-05 Thread Sandro Bonazzola
Il giorno ven 2 set 2022 alle ore 17:26 Diego Ercolani < diego.ercol...@ssis.sm> ha scritto: > Anyone can give a hint please? > You can use the procedure at https://access.redhat.com/solutions/2212601 In your case: # hosted-engine --clean-metadata --host-id=2 --force-clean should work --