The oVirt settings on the Gluster have server quorum enabled . If quorum is less than 50% +1 servers -> all bricks will shutdown. If the compute-only node is part of the TSP (Gluster's cluster) , it will also be calculated for quorum and in most cases you don't want that. If it's so - just remove it (from the main nodes) from the TSP. Best Regards, Strahil Nikolov В неделя, 23 януари 2022 г., 05:13:25 Гринуич+2, David White <dmwhite823@protonmail.com> написа: 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@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@ovirt.org> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZLDTUYRNCZYCU...