Nicolas,  I have the same setup dedicated physical system running engine on CentOS 6.6 three hosts running CentOS 7.1 with Gluster and KVM, and firewall is disabled on all hosts.  I also followed the same documents to build my environment so I assume they are very similar.  I have on occasion had the same errors and have also found that "ctdb rebalanceip <floating ip>" is the only way to resolve the problem.  I intend to remove ctdb since it is not needed with the configuration we are running.  CTDB is only needed for hosted engine on a floating NFS mount, so you should be able change the gluster storage domain mount paths to "localhost:<name>".  The only thing that has prevented me from making this change is that my environment is live with running VM's.  Please let me know if you go this route.

Thank you,
Tim Macy

On Thu, Aug 6, 2015 at 8:41 AM, Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Le 06/08/2015 14:26, Sahina Bose a écrit :

- "Host serv-vm-al03 cannot access the Storage Domain(s) <UNKNOWN>
attached to the Data Center"
Just by waiting a couple of seconds lead to a self heal with no action.

- Repeated "Detected change in status of brick
serv-vm-al03:/gluster/data/brick of volume data from DOWN to UP."
but absolutely no action is made on this filesystem.

This is coming from the earlier issue where the Host status was marked
Down, the engine sees these bricks as being Down as well, and hence the
state change messages

 OK : When I read "Host ... cannot access the Storage Domain ... attached to the Data Center", and according to the setup described earlier (NFS on ctdb on gluster), is it correct to translate it into
"this host can not NFS-mount the storage domain"?

In which case it will help me to narrow down my debugging.


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