Bug 1658930 - firewall rules for horizon port 80 and 443 is not open on Haproxy node
Summary: firewall rules for horizon port 80 and 443 is not open on Haproxy node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: z5
: 13.0 (Queens)
Assignee: Emilien Macchi
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks: 1661074
TreeView+ depends on / blocked
 
Reported: 2018-12-13 08:10 UTC by Sadique Puthen
Modified: 2022-03-13 16:57 UTC (History)
12 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.0.7-22.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1661074 (view as bug list)
Environment:
Last Closed: 2019-03-14 13:55:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1808530 0 None None None 2018-12-14 13:38:13 UTC
OpenStack gerrit 625600 0 None MERGED Fix horizon's iptables rules for haproxy when split off a separate role 2020-04-16 11:37:32 UTC
Red Hat Issue Tracker OSP-13834 0 None None None 2022-03-13 16:57:12 UTC
Red Hat Product Errata RHBA-2019:0448 0 None None None 2019-03-14 13:55:19 UTC

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
Note You need to log in before you can comment on or make changes to this bug.