I actually had the opposite problem - I (not knowing) elected to say “Yes” (default
answer) to “iptables was detected on your computer, do you wish setup to configure it?”
which then put in the oVirt iptables rules, which assume the standard Gluster TCP ports…
Since I am running hyperconverged and had followed the instructions found at:
http://www.ovirt.org/Features/Self_Hosted_Engine_Hyper_Converged_Gluster_...
which ends up changing the Gluster ports, then I experienced a fault with Gluster where it
lost quorum and went read-only since the firewall on the hosts were blocking Gluster
communications...
On Jan 6, 2016, at 11:10 AM, Sahina Bose <sabose(a)redhat.com> wrote:
Also, worth checking that glusterd ports are open on the gluster hosts (we had an issue
where HE install overrides glusterd ports and gluster volume was inaccessible)