Container sync: PUT returns HTTP error 400 when existing object has same x-timestamp
Bug #1029156 reported by
Philip Peshin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Philip Peshin | ||
Bug Description
Steps to reproduce:
1) Set two containers container 1 and container 2 for mutual sync as per http://
2) store an object in container 1
3) container sync puts the object from container1 to container2, receives HTTP 200 (ok)
4) container sync tries to put object back from container2 to container1. It supposed to be the same object, that is checked by comparing x-timestamp. Expected result should be HTTP 202 (accepted). But because of the bug error 400 is returned and logged into proxy.error. Container sync retries infinitely and fails
swift (1.6.0)
| Changed in swift: | |
| assignee: | nobody → Philip Peshin (ppeshin) |
| status: | New → In Progress |
Revision history for this message
| Philip Peshin (ppeshin) wrote | #1 |
| Changed in swift: | |
| status: | In Progress → Fix Committed |
| Changed in swift: | |
| milestone: | none → 1.6.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Here is a patch - there was a typo in format string