Description of problem: On an SSL enabled overcloud the Neutron api returns http URL openstack catalog show neutron +-----------+------------------------------------------------------+ | Field | Value | +-----------+------------------------------------------------------+ | endpoints | regionOne | | | publicURL: https://[2001:db8:ca2:4::10]:13696 | | | internalURL: http://[fd00:fd00:fd00:2000::14]:9696 | | | adminURL: http://[fd00:fd00:fd00:2000::14]:9696 | | | | | name | neutron | | type | network | +-----------+------------------------------------------------------+ curl -s -H "X-Auth-Token: $OS_TOKEN" https://172.16.18.25:13042 | python -m json.tool { "versions": [ { "id": "v2.0", "links": [ { "href": "http://[2001:db8:ca2:4::10]:13696/v2.0", "rel": "self" } ], "status": "CURRENT" } ] } Version-Release number of selected component (if applicable): openstack-neutron-9.0.0-0.20160929051647.71f2d2b.el7ost.noarch
Testing fails with the current build. I believe in order to be able to verify this we also need a fix for BZ#1384340 which is still in NEW state. curl -s -H "X-Auth-Token: $OS_TOKEN" https://172.16.18.25:13696 | python -m json.tool { "versions": [ { "id": "v2.0", "links": [ { "href": "http://172.16.18.25:13696/v2.0", "rel": "self" } ], "status": "CURRENT" } ] }
Marius, do you have a specific puppet patch on your mind?
(In reply to Ihar Hrachyshka from comment #4) > Marius, do you have a specific puppet patch on your mind? Yes, it looks that this one fixes addresses the issue: https://review.openstack.org/#/c/400591/
Marius, puppet-tripleo doesn't have a patches branch. In other words, patches are automatically synced from upstream. Putting a needinfo on Mike Burns who I hear deals with the syncs.
This has landed in the latest build and canbe verified: { "versions": [ { "id": "v2.0", "links": [ { "href": "https://172.16.18.25:13696/v2.0", "rel": "self" } ], "status": "CURRENT" } ] }
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