Yeah. That did the trick. What I did was:
Enable global maintenance.
On every affected host:
# systemctl stop ovirt-ha-agent
# hosted-engine --clean-metadata --host-id=1 --force-clean (repeat for every id)
Finally start the stopped ha-agents.
Check the status:
# hosted-engine --vm-status
Disable
Hi,
the stale records are not an issue at all. You can remove them for
visually cleaner reports (hoste-engine --clean-metadata command, check
the man page), but it makes no difference to the algorithms.
Best regards
Martin Sivak
On Thu, May 2, 2019 at 11:31 AM Andreas Elvers
wrote:
>
> I have
I did that. There is no change. Node01,02 and 03 are still present in
"hosted-engine --vm-status".
> In a Red Hat Solution , it is recommended to restart ovirt-ha-agent &
> ovirt-ha-broker.
>
> I usually set the global maintenance and wait 20s-30s . Then I just stop on
> all nodes
> ovirt-ha-
In a Red Hat Solution , it is recommended to restart ovirt-ha-agent &
ovirt-ha-broker.
I usually set the global maintenance and wait 20s-30s . Then I just stop on all
nodes ovirt-ha-agent.service & ovirt-ha-broker.service . Once everywhere is
stopped, start the 2 services on all nodes and wait
4 matches
Mail list logo
