Description of problem: http endpoint returned instead of https when cinder service calls are made $ curl -g -i -X GET https://node1.example.com:8776/ -H "Accept: application/json" -H "User-Agent: python-keystoneclient" HTTP/1.1 200 OK Content-Type: application/json Content-Length: 334 Date: Mon, 29 Jun 2015 15:59:35 GMT {"versions": [{"status": "CURRENT", "updated": "2012-01-04T11:33:21Z", "id": "v1.0", "links": [{"href": "http://node1.example.com:8776/v1/", "rel": "self"}]}, {"status": "CURRENT", "updated": "2012-11-21T11:33:21Z", "id": "v2.0", "links": [{"href": "http://node1.example.com:8776/v2/", "rel": "self"}]}]} $ keystone endpoint-list | egrep "8776" | awk -F\| '{print $3,$4,$5,$6}' RegionOne https://node1.example.com:8776/v2/%(tenant_id)s https://i.node1.example.com:8776/v2/%(tenant_id)s https://i.node1.example.com:8776/v2/%(tenant_id)s RegionOne https://node1.example.com:8776/v1/%(tenant_id)s https://i.node1.example.com:8776/v1/%(tenant_id)s https://i.node1.example.com:8776/v1/%(tenant_id)s Version-Release number of selected component (if applicable): openstack-cinder-2014.1.4-1.el7ost.noarch python-cinder-2014.1.4-1.el7ost.noarch python-cinderclient-1.0.9-1.el7ost.noarch How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: The http endpoint is listed. Expected results: service call should obtain https endpoint . Additional info: This behaviour is noticed for nova & glance too . We suspect this to be caused due to behaviour mentioned in https://bugs.launchpad.net/cinder/+bug/1384379
Do we have an update on this?
(In reply to William from comment #5) > Do we have an update on this? (In reply to William from comment #5) > Do we have an update on this? I believe it's already fixed in Kilo (7.0), see this https://review.openstack.org/#/c/159374/ This bug is detected on 5.0 but targeted for 8.0 most probably because this is a default. Do you need to backport this fix to 5.0?
(In reply to Sergey Gotliv from comment #6) > (In reply to William from comment #5) > > Do we have an update on this? > > (In reply to William from comment #5) > > Do we have an update on this? > > I believe it's already fixed in Kilo (7.0), see this > https://review.openstack.org/#/c/159374/ > > This bug is detected on 5.0 but targeted for 8.0 most probably because this > is a default. Do you need to backport this fix to 5.0? Sergey, yes please. Is there anything you need me to do to facilitate?
> Is there anything you need me to do to facilitate? Thanks for the offer, no need for the moment. :-)
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/RHBA-2015-2686.html