CONF.auth_url option used inconsistently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Low
|
Nicolas Simonds |
Bug Description
The Glance registry API will look at the running environment for an $OS_AUTH_URL variable, and if set, it will adjust its auth strategy accordingly. But even if the value is set in the environment, only the value in the config file is used. This is inconsistent.
To reproduce:
* Set up a config file for a glance CLI tool, e.g., the glance-scrubber with no "auth_strategy" or "auth_url" options set
* set an $OS_AUTH_URL environment variable that points to a running Keystone instance
* Try to use the configured tool, e.g., spool up some delayed deletes and try to get the scrubber to purge them
Expected results:
* It should automagically figure out based on the environment that it should talk to Keystone, and should attempt to auth against it
Actual results:
* No auth_url ends up getting set, and glance-scrubber falls flat on its face when trying to update the registry
Changed in glance: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
importance: | Undecided → Low |
Changed in glance: | |
milestone: | kilo-2 → 2015.1.0 |
Hi Nicolas,
The scrubber uses registry v1 client which takes the auth_url from env variables. Could you be bit more specific how do you see this happening, or do you mean that the services does not obey the auth url specified in the client's environment?