Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1191114

Summary: VXLAN traffic port (4789) and GRE should allowed between all nodes when tunnelling is enabled
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: openstack-puppet-modulesAssignee: Ivan Chavero <ichavero>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0 (Juno)CC: sclewis, tfreger, vvaldez, yeylon
Target Milestone: ga   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2015.1-0.3.dev1565.gd1211af.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:21:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Itzik Brown 2015-02-10 13:32:48 UTC
Description of problem:
When using Packstack to install Openstack it runs iptables to allow traffic between Network nodes and compute nodes but not between compute nodes.

Staypuft, on the other hand opens port 4789 without restrictions.

Version-Release number of selected component (if applicable):
RHEL7.0

How reproducible:


Steps to Reproduce:
1.After installation run iptables -S |grep 4789 (For VXLAN) Or iptables -S|grep -i gre (For GRE)
2. Verify that there are rules just between the Network nodes and the compute nodes
3.

Actual results:
As described above.

Expected results:
When tunnelling is enabled there should be rules to allow tunnelled traffic between all the nodes in the cloud.

Additional info:

Comment 4 Ivan Chavero 2015-06-19 07:17:57 UTC
this bug is fixed in the latest version

Comment 8 Itzik Brown 2015-07-07 13:39:57 UTC
Verified VXLAN
packstack Kilo 2015.1.dev1589.g1d6372f

Comment 10 errata-xmlrpc 2015-08-05 13:21:09 UTC
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.

https://access.redhat.com/errata/RHEA-2015:1548