glance-cache-manage talks to image endpoint instead of the specified host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
High
|
Kairat Kushaev | ||
Newton |
Fix Committed
|
Medium
|
Kairat Kushaev |
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_
Initial bug description:
If we want glance-cache-manage commands to communicate over internalURL, it doesn't support. It always use publicURL for communication.
summary: |
- glance-cache-manage --debug --list-cached doesn't support for - internalURL + glance-cache-manage commands doesn't support for internalURL |
Changed in glance: | |
assignee: | nobody → Sasikiran (sasikiran-vaddi) |
Changed in glance: | |
assignee: | Sasikiran (sasikiran-vaddi) → nobody |
description: | updated |
Changed in glance: | |
importance: | Undecided → High |
status: | Incomplete → Fix Committed |
Changed in glance: | |
status: | Fix Committed → In Progress |
@Sasikiran: Can you please tell us what you exactly mean by telling glance-cache-manage is not communicating over the internal url? cache-manage, you can set it using --os-auth-url along with glance- manage- cache. The store specific endpoints are used by Glance to communicate with the backend.. That does not set glance-cache-manage to use it as cache is cleared directly from glance.
Did you mean for communication via keystone?
If you intend to use the internalURL for glance-
Thanks.