yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #58621
[Bug 1634486] Re: glance-cache-manage talks to image endpoint instead of the specified host
Reviewed: https://review.openstack.org/393229
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=616060db65ac3f12c0a71fd21f8156c6e993d7ab
Submitter: Jenkins
Branch: master
commit 616060db65ac3f12c0a71fd21f8156c6e993d7ab
Author: kairat_kushaev <kkushaev@xxxxxxxxxxxx>
Date: Thu Nov 3 13:21:05 2016 +0300
Do not use service catalog for cache client
Previously cache client used endpoints from service catalog to
request cache items from node. It works perfectly on devstack
but it doesn't work when an OpenStack cloud is deployed with HA
(3/5/7 controllers). We need to use -H option instead.
This option makes cache management client interact with the local
endpoint which is more appropriate as image cache is local to
each node/controller.
Change-Id: I355fb36d9af7e06dcac70b8263dc1a2b915ffc8f
Closes-Bug: #1634486
** Changed in: glance
Status: In Progress => Fix Released
--
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:
Fix Released
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
References