deleting a message after claiming it fails
Bug #1325032 reported by
Sriram
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Python client library for Zaqar |
Fix Released
|
Critical
|
Sriram | ||
| Juno |
Fix Released
|
Critical
|
Sriram | ||
Bug Description
when deleting a message, the client fails to provide the claim_id along with the message id. This leads to a 403 status from marconi, as the client didn't supply needed credentials to delete a claimed message.
The fix would also need to include a unit test, that proves that the bug was fixed.
Below is the response from marconi when attempting to delete a claimed message.
Attached:
http://
| summary: |
- deleting a message after claiming fails + deleting a message after claiming it fails |
Revision history for this message
| Kurt Griffiths (kgriffs) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-marconiclient (master) | #2 |
| Changed in python-marconiclient: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-marconiclient (master) | #3 |
| Changed in python-marconiclient: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
The problem appears to stem from reconstructing the URI rather than simply using the href returned for that message; the href includes the claim ID, while the reconstructed URI does not.