Bug 961645
Summary: | PRD33 - [RHEVM-RHS] Bootstrapping should set iptables rules, allowing gluster process on RHS Nodes | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | SATHEESARAN <sasundar> | |
Component: | ovirt-engine-webadmin-portal | Assignee: | Sahina Bose <sabose> | |
Status: | CLOSED ERRATA | QA Contact: | Rejy M Cyriac <rcyriac> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.2.0 | CC: | acathrow, ecohen, grajaiya, iheim, jkt, rcyriac, Rhev-m-bugs, rhs-bugs, sabose, scohen, shtripat, thildred | |
Target Milestone: | --- | Keywords: | Improvement | |
Target Release: | 3.3.0 | Flags: | scohen:
Triaged+
|
|
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | gluster | |||
Fixed In Version: | is2 | Doc Type: | Enhancement | |
Doc Text: |
On Red Hat Storage nodes, gluster processes were blocked by iptables rules, so volumes could not be mounted. This update adds the ports required for GlusterFS brick processes (49152 to 49251) and for accessing Gluster volumes (port 111) in the iptables configuration file. It also leaves the old ports (24009 to 24108) open for compatibility with older servers.
|
Story Points: | --- | |
Clone Of: | ||||
: | 977619 (view as bug list) | Environment: |
virt rhev integration
|
|
Last Closed: | 2014-01-21 17:20:56 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 977619 |
Description
SATHEESARAN
2013-05-10 07:36:14 UTC
Available in 3.3 now Verified on RHEVM 3.3 IS11 Build, with RHS 2.1 (glusterfs-server-3.4.0.24rhs-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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 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. http://rhn.redhat.com/errata/RHSA-2014-0038.html |