yahoo-eng-team team mailing list archive

[Nicolas Simonds <1314354@xxxxxxxxxxxxxxxxxx>]

I didn't respond because you asked a question that could trivially be
answered by reproducing the bug as per the original bug report.  If you
guys are going to make "making contributors answer questions that they
have already answered" a prerequisite for handling anything, it's going
to take a really long time for anything to get done.

** Changed in: glance
       Status: Invalid => In Progress

** Changed in: glance
     Assignee: (unassigned) => Nicolas Simonds (nicolas.simonds)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1314354

Title:
  CONF.auth_url option used inconsistently

Status in OpenStack Image Registry and Delivery Service (Glance):
  In Progress

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1314354/+subscriptions