We are not creating the Heat cfn api endpoint in the undercloud. We should go ahead and create the endpoint since we are enabling the service. The endpoint is also needed if you are using deployed servers and want to configure the Heat polling and signaling to go over the public endpoints in the case where the ctlplane is not routable. In such a scenario, there needs to be a public endpoint for the cfn api created.
*** Bug 1435211 has been marked as a duplicate of this bug. ***
technically this is not a blocker, since we've documented using swift as the default signaling instead of CFN. since there are already public endpoints for swift created in the undercloud, this patch doesnt need to block 11.
i can't think of any reason why one would have to use CFN signaling. However, if there was one, this public endpoint would be needed.
Removing blocker flag, let's try to still get it in OSP11.
stable/ocata backport merged
Verified on build 2017-04-20.2
[stack@undercloud-0 ~]$ . stackrc && openstack catalog list | grep heat-cfn
| heat-cfn | cloudformation | regionOne
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.