Bug 1600399
Summary: | Project purge deletes ALL images | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Sandeep Yadav <sandyada> |
Component: | python-openstackclient | Assignee: | Julie Pichon <jpichon> |
Status: | CLOSED ERRATA | QA Contact: | Shai Revivo <srevivo> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 12.0 (Pike) | CC: | apevec, jamsmith, lhh, srevivo |
Target Milestone: | z3 | Keywords: | Triaged, ZStream |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-openstackclient-3.12.1-1.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Prior to this update, the "project purge" command deleted all images regardless of which project owned it.
This update fixes a mismatch between deletion code for Glance V1 and V2. It adds code specific to Glance V2 to handle the deletion correctly.
Now the "project purge" command only deletes images owned by the specified project ID when run by an admin user.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-08-20 12:54:28 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
Sandeep Yadav
2018-07-12 07:46:41 UTC
Thank you for the detailed bug report. Unfortunately 3.13 is a Queens/OSP13 release ( https://releases.openstack.org/teams/openstackclient.html#team-queens-python-openstackclient ) and can't be included in OSP12. However it looks like this particular patch was already backported to Pike and is included in the next point release, 3.12.1. I can see the package for this is already built downstream and would expect it to be included in the next OSP12 maintenance release. 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/RHBA-2018:2521 |