Thank you very much.
Over the course of troubleshooting, I did wind up updating (and rebooting) the engine.
The issue "magically" resolved itself a few hours after I sent this email with
the two Gluster nodes. They became operational again, and thus, I wound up having enough
compute power to bring everything back online. That said, the compute-only node is still
not operational. I'll take a look at the "gluster pool list" command. Thank
you for that.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, January 22nd, 2022 at 5:48 PM, Strahil Nikolov <hunter86_bg(a)yahoo.com>
wrote:
Check the situation with the gluster storage.Also, you can check if
the compute-only node is added to the gluster trsuted storage pool:gluster pool list
(should show localhost -+ 2 more).
Also, consider upgrading the engine. Most probably the engine cannot
connect to the vdsm and vdsm-gluster and this makes the whole situation worse.
Best Regards,Strahil Nikolov
> On Sat, Jan 22, 2022 at 23:15, David White via
Users<users(a)ovirt.org> wrote:_______________________________________________
>
> Users mailing list -- users(a)ovirt.org
>
> To unsubscribe send an email to users-leave(a)ovirt.org
>