On Tue, Sep 20, 2022 at 4:50 AM David White via Users wrote:
>
> This is resolved.
> I manually shutdown each VM, and then from within oVirt, I went to the host,
> and in the upper corner of the page when looking at the host, I clicked on
> 'Confirm Host has been rebooted'.
>
> This allowed oVir
This is resolved.
I manually shutdown each VM, and then from within oVirt, I went to the host,
and in the upper corner of the page when looking at the host, I clicked on
'Confirm Host has been rebooted'.
This allowed oVirt to then recognize that the VMs were down, and I was able to
bring them
Restarting the `vdsmd` service on 1 of the problematic hosts brought that host
back, and ovirt can see it.
But that did not fix the problem on the last remaining host. I'm still
troubleshooting...
Sent with Proton Mail secure email.
--- Original Message ---
On Monday, September 19th,
I tried rebooting the engine to see if that would magically solve the problem
(worth a try, right?). But as I expected, it didn't help.
Now one of the hosts is in a "Non Responsive" state and the other is
permanently in a "Connecting" state. All VMs associated with those 2 hosts now
show a ques
4 matches
Mail list logo
