Description of problem: On an SSL enabled overcloud the heat-cfn api returns http URL: openstack catalog show heat-cfn +-----------+--------------------------------------------+ | Field | Value | +-----------+--------------------------------------------+ | endpoints | RegionOne | | | publicURL: https://172.16.18.25:13005/v1 | | | internalURL: http://10.0.0.5:8000/v1 | | | adminURL: http://10.0.0.5:8000/v1 | | | | | name | heat-cfn | | type | cloudformation | +-----------+--------------------------------------------+ curl -s -H "X-Auth-Token: $OS_TOKEN" https://172.16.18.25:13005/ | python -m json.tool { "versions": [ { "id": "v1.0", "links": [ { "href": "http://172.16.18.25:13005/v1/", "rel": "self" } ], "status": "CURRENT" } ] } Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-5.0.0-0.20160929150845.4cdc4fc.el7ost.noarch openstack-heat-api-cfn-7.0.0-0.20160926200847.dd707bc.el7ost.noarch How reproducible: 100%
This is related to bug#1370018, which is a higher-level bug that spans multiple components that are having this problem. The upstream fix for this has merged into master already. Juan - does this need to be proposed for stable/newton so it can get pulled into OSP10?
backported it to stable/newton
now looks something like this: {"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "https://[2620:52:0:13b8:5054:ff:fe3e:1]:13005/v1/", "rel": "self"}]}]}
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