OpenStack Heat

heat-api fails to respect clients_keystone.insecure config when performing Keystone discovery

Bug #1547278 reported by Travis Truman on 2016-02-19

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Heat	In Progress	Undecided	Travis Truman	OpenStack Heat no-milestone-taged-bugs

When starting heat-api that is configured to use a Keystone auth_uri secured with a self-signed certificate and with config like:

[clients_keystone]
insecure = True
endpoint_type = internalURL
auth_uri = https://172.29.236.100:5000

heat-api fails to start as it fails in common/endpoint_utils#get_auth_uri

Cause of the failure appears to be that the keystoneclient.Discover class is not configured properly to pass through the insecure configuration.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-02-19: Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/282120

Changed in heat:
assignee:	nobody → Travis Truman (travis-truman)
status:	New → In Progress

Revision history for this message

Travis Truman (travis-truman) wrote on 2016-02-19:

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-02-22: Change abandoned on heat (master)

Change abandoned by Travis Truman (automagically) (<email address hidden>) on branch: master
Review: https://review.openstack.org/282120
Reason: Abandon as https://review.openstack.org/#/c/282321/ has merged

Rico Lin (rico-lin) on 2018-05-07

Changed in heat:
milestone:	none → no-priority-tag-bugs

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.