I did exactly the same mistake with my standalone GlusterFS cluster and now need to take down all Storage Domains in order to fix this mistake. 
Probably, worth to add a few words about this in Installation guide!

On Tue, Dec 12, 2017 at 4:52 PM, Simone Tiraboschi <stirabos@redhat.com> wrote:


On Mon, Dec 11, 2017 at 8:44 PM, Beau Sapach <bsapach@ualberta.ca> wrote:
We've been doing some experimenting with gluster, and have built a stand-alone gluster cluster (not managed by oVirt).  We've been able to create a storage domain backed by that gluster cluster and run VMs with their disks on that storage.

The problem we have is that when we take a gluster node down for updates, maintenance etc. the entire storage domain goes offline in oVirt.  Other gluster clients, that is servers connecting directly to the gluster cluster don't seem to notice if one node goes offline.

Is anyone else using gluster storage in oVirt that is not managed within oVirt?

Did you set also the backup-volfile-servers mount option?
 


--
Beau Sapach
System Administrator | Information Technology Services | University of Alberta Libraries


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users