Description of problem: When we install undercloud by 'openstack undercloud install', we see that the undercloud node has the following rule in iptables. ~~~ -A INPUT -p tcp -m multiport --dports 80,443 -m state --state NEW -m comment --comment "126 horizon ipv4" -j ACCEPT ~~~ However, we don't have Horizon deployed/configured in undercloud node, which means that this iptables rule is useless. ~~~ [stack@undercloud-0 ~]$ rpm -qa | grep horizon puppet-horizon-12.4.0-1.el7ost.noarch [stack@undercloud-0 ~]$ ~~~ How reproducible: Always Steps to Reproduce: 1. Install undercloud 2. See iptables-save to see configured rules Actual results: iptables-save has an ACCEPT rule about tcp/80 and tcp/443, which is used for horizon Expected results: iptables-save doesn't have an ACCEPT rules about tcp/80 and tcp/443, which is used for horizon Additional info:
I proposed a possible fix[1] for stable/rocky. [1] https://review.opendev.org/#/c/696215/ However, I'm not sure whether I'm doing the correct thing because I don't understand the reason why we have horizon configuration there. (It seems that we had horizon deployed in undercloud node in old releases?) It would be nice if I can ask eng to have a look about that.
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-2020:0760