Glance

glance registry client searches for "image" endpoint when authenticating

Bug #1187888 reported by Alex Meade on 2013-06-05

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Glance	Fix Released	Medium	Alex Meade	Glance 2013.2 "havana"

Bug Description

When using admin credentials to communicate with glance registry, glance api may throw a NoServiceEndpoint error when the admin user does not have an "image" endpoint in their service catalog.

It turns out that Glance api will always search for an "image" endpoint via glance registry client when authenticating in order to talk to glance registry. This is incorrect since it will not be using this endpoint and the user may not even have an "image" endpoint in their service catalog (and shouldn't need to).

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-06-05: Fix proposed to glance (master)

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

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-06-10: Fix merged to glance (master)

Reviewed: https://review.openstack.org/31836
Committed: http://github.com/openstack/glance/commit/d17e87ff7fb5918c9576009e04cc3996bfd352ea
Submitter: Jenkins
Branch: master

commit d17e87ff7fb5918c9576009e04cc3996bfd352ea
Author: Alex Meade <email address hidden>
Date: Wed Jun 5 14:56:14 2013 -0400

Pass configure_via_auth down to auth plugin

    Pass down the configure_via_auth value to the auth plugin to say whether or not
    it should look in the service catalog for the glance registry endpoint. This
    stops authentication by glance registry client from needlessly looking for an
    "image" service endpoint when the user may not have it in their service catalog.

Fixes bug 1187888

Change-Id: I1c4a726ff0d6a345a27446500135f4f27cea5e39