Bug 1658930

Summary: firewall rules for horizon port 80 and 443 is not open on Haproxy node
Product: Red Hat OpenStack Reporter: Sadique Puthen <sputhenp>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aschultz, augol, bperkins, cgoncalves, jjoyce, jschluet, mburns, michele, pkomarov, slinaber, sputhenp, tvignaud
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.7-22.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1661074 (view as bug list) Environment:
Last Closed: 2019-03-14 13:55:07 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:
Bug Depends On:    
Bug Blocks: 1661074    

Comment 2 Sadique Puthen 2018-12-13 10:08:52 UTC 
Octavia services are running on composable role and Haproxy on different one.

Octavia ports are open by iptables on Haproxy node, but not open on where Octavia API runs. Does this need a different bug or can we fix it here?
Comment 3 Alex Schultz 2018-12-13 15:40:03 UTC 
This might not be a supported configuration as we don't specifically configure firewall rules based on HAproxy's location as we assume HAProxy is always on the same host as the api services.  It's likely that there might need to be a custom set of rules created for this architecture.  Slightly related would be Bug 1445766
Comment 23 Amit Ugol 2019-03-11 05:01:48 UTC 
Fix is in place.
Comment 25 errata-xmlrpc 2019-03-14 13:55:07 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/RHBA-2019:0448