On Wed, May 27, 2020 at 4:52 PM Randall Wood <rwood@forcepoint.com> wrote:
I have a three node oVirt 4.3.7 cluster that is using GlusterFS as the underlying storage (each oVirt node is a GlusterFS node). The nodes are named ovirt1, ovirt2, and ovirt3. This has been working wonderfully until last week when ovirt2 crashed (it is *old* hardware; this was not entirely unexpected).

Now I have this situation: all three oVirt nodes are acting as if the GlusterFS volumes only exist on ovirt2. The bricks on all three nodes appear to be in sync.

I *think* this began happening after I restarted ovirt2 (once hard, and once soft) and then restarted glusterd (and only glusterd) on ovirt1 and ovirt3 after `gluster-eventsapi status` on those two nodes showed inconsistent results (this had been used with success before).

How can I make the oVirt nodes read and write from their local bricks?


Supposing all the rest is ok and gluster optimized for oVirt, you can check the "cluster.choose-local" parameter that is false by default in oVirt.
Anyway an interesting recent thread here, also to manage scenarios where not all your nodes are HCI:

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/OMAAERV4IUISYEWD4QP5OAM4DK4JTTLF/

HIH,
Gianluca