Description of problem: The nova_ec2 is configured in haproxy config while the backend services are down: Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-2.0.0-12.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy overcloud 2. grep -A5 ec2 /etc/haproxy/haproxy.cfg Actual results: [root@ctrl-r00-00 heat-admin]# grep -A5 ec2 /etc/haproxy/haproxy.cfg listen nova_ec2 bind 10.0.0.5:8773 transparent bind 172.16.18.25:8773 transparent server ctrl-r00-00 10.0.0.10:8773 check fall 5 inter 2000 rise 2 server ctrl-r01-01 10.0.0.11:8773 check fall 5 inter 2000 rise 2 server ctrl-r02-02 10.0.0.12:8773 check fall 5 inter 2000 rise 2 [root@ctrl-r00-00 heat-admin]# curl 10.0.0.10:8773 curl: (7) Failed connect to 10.0.0.10:8773; Connection refused Expected results: According to https://review.openstack.org/#/c/316360/ we should expect Nova EC2 to be remved so I expect it to be removed from haproxy as well. Additional info:
This landed in OSP10 via https://review.openstack.org/#/c/316361/
(In reply to Michele Baldessari from comment #2) > This landed in OSP10 via https://review.openstack.org/#/c/316361/ Shouldn't this bug be in POST if we have a patch upstream?
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://rhn.redhat.com/errata/RHEA-2016-2948.html