yahoo-eng-team team mailing list archive

[Ian Cordasco <ian.cordasco@xxxxxxxxxxxxx>]

So this bug does affect newton and earlier, but newton is presently the
only stable branch that is not restricted to critical and security
fixes. This isn't a terribly critical bug, in my evaluation, and as such
I've only nominated this to be backported to newton.

** Also affects: glance/newton
   Importance: Undecided
       Status: New

** Changed in: glance/newton
     Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  glance-cache-manage talks to image endpoint instead of the specified
  host

Status in Glance:
  In Progress
Status in Glance newton series:
  New

Bug description:
  Corrected bug description (based on the comments below):
  In Glance, image cache is local to each node. And, hence, image cache management must be performed on each node locally. This is supported by providing a specific host using '-H' or '--host' argument to glance-cache-manage utility.

  However, due to a bug glance-cache-manage currently ignores the
  provided host and fetches the image endpoint to manage the cache.
  While this does manage the cache, we don't know what node is being
  managed here. This can be fixed by passing 'configure_via_auth=False'
  when creating the image cache client. This ensures that image endpoint
  is not fetched and the provided host is used.

  Initial bug description:
  If we want glance-cache-manage commands to communicate over internalURL, it doesn't support. It always use publicURL for communication.

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