glance registry client searches for "image" endpoint when authenticating
Bug #1187888 reported by
Alex Meade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Alex Meade |
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).
Changed in glance: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/31836
Review: https:/