Red Hat Bugzilla – Bug 961645
PRD33 - [RHEVM-RHS] Bootstrapping should set iptables rules, allowing gluster process on RHS Nodes
Last modified: 2016-02-10 13:58:48 EST
Description of problem:
On RHS Nodes, gluster processes are blocked, by iptables rules, and so volumes could not be mounted.
Bootstrapping, should take care of adding iptables rules for gluster and other related processes.
Version-Release number of selected component (if applicable):
RHS 2.1 - glusterfs 22.214.171.124rhs-1
Steps to Reproduce:
1. Create a gluster cluster in RHEVM
2. Add RHS nodes to gluster cluster
3. Create a volume and try to make it as Storage Domain.
Unable to mount the storage domain [ gluster volume ], because iptables blocking
should able to mount the storage domain [ gluster volume ]
After performing iptables flush, the storage domain [gluster volume] could be mounted
Available in 3.3 now
Verified on RHEVM 3.3 IS11 Build, with RHS 2.1 (glusterfs-server-126.96.36.199rhs-1.el6rhs)
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.