Bug 1660734

Summary:	Add glance cache-manage utility
Product:	Red Hat OpenStack	Reporter:	Abhishek Kekane <akekane>
Component:	openstack-glance	Assignee:	Abhishek Kekane <akekane>
Status:	CLOSED ERRATA	QA Contact:	Mike Abrams <mabrams>
Severity:	medium	Docs Contact:	Kim Nylander <knylande>
Priority:	medium
Version:	15.0 (Stein)	CC:	abishop, eglynn
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-glance-18.0.1-0.20190420013840.f772321.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:19:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Abhishek Kekane 2018-12-19 05:53:46 UTC

Description of problem:

In Rocky, the v1 dependent glance-cache-manage command was removed while removing Images API v1 entry points.

In Stein, as per Edge computing architecture, glance cache will be enabled on far-edge nodes. Hence it will be good to add glance-cache-manage utility using v2 API in glance. This utility will have the same interface as Queens glance-cache-manage utility [0] so far as possible.

[0] https://docs.openstack.org/glance/queens/cli/glancecachemanage.html


Version-Release number of selected component (if applicable):
15

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Abhishek Kekane 2018-12-19 05:55:38 UTC

Upstream Blueprint: https://blueprints.launchpad.net/glance/+spec/cache-manage

Upstream specs-lite: https://review.openstack.org/#/c/609331
Approved and merged.

Comment 3 Abhishek Kekane 2018-12-19 06:29:38 UTC

Patch submitted to master branch.
https://review.openstack.org/626097 Add cache-manage utility using v2 API

Comment 14 errata-xmlrpc 2019-09-21 11:19:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811