Bug 917059
| Summary: | member-delete incorrect status codes on delete already deleted or invalid entry | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> | |
| Component: | openstack-glance | Assignee: | Eoghan Glynn <eglynn> | |
| Status: | CLOSED ERRATA | QA Contact: | Attila Fazekas <afazekas> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 2.0 (Folsom) | CC: | eglynn | |
| Target Milestone: | snapshot5 | Keywords: | Triaged | |
| Target Release: | 2.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 923395 (view as bug list) | Environment: | ||
| Last Closed: | 2013-04-04 20:23:50 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 923395 | |||
|
Description
Attila Fazekas
2013-03-01 15:17:46 UTC
The problem is that the image member is referred to without checking if it actually exists: https://github.com/openstack/glance/blob/stable/folsom/glance/registry/api/v1/members.py#L284 leading to an IndexError on the list dereference in the non-existing case. The fix is obvious and highly self-contained, hence very low-risk. When forward-porting my initial fix to upstream master, I discovered that it has already been fixed there: https://review.openstack.org/14210 Hence the task just collapses down to a master->stable backport of an existing fix. Abandoning my own patch, and backporting the original fix. Original fix backported and proposed to stable/folsom upstream: https://review.openstack.org/24116 Proposed internally as: https://code.engineering.redhat.com/gerrit/#/c/3951/ The 500 error response fixed. But, deleting an already deleted member still succeeds. I got 204, but the expected 404. Did you created a different issue for that ? Attila, I missed the second intertwined issue. The 204 versus 404 should probably have been separate from the get-go So can you clone off a separate issue for it, and I'll take a look at later this evening? (I suspect probably a simple issue around the lingering deleted=1 row in the DB, so should probably be quickly fixable ...) Cheers, Eoghan So the 500 response is solved , the cloned bug for the other issue https://bugzilla.redhat.com/show_bug.cgi?id=923395 is here. 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. http://rhn.redhat.com/errata/RHSA-2013-0707.html |