EC: etag of range request is not consistent
Bug #1496234 reported by
clayg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Mahati Chamarthy |
Bug Description
I think the etag on some range requests is coming off the backend headers directly, maybe not being translated in the proxies "fixup backend ec headers" dance.
I added an assertion to an existing functest [1] and it works on repl but fails on ec [2].
1. https:/
2. i.e SWIFT_TEST_
Changed in swift: | |
status: | New → Confirmed |
Changed in swift: | |
assignee: | nobody → Mahati (mahati-chamarthy) |
To post a comment you must log in.
reversing the parameters in the assert: https:/ /gist.github. com/MahatiC/ 912eb17858a0b15 05ef0 seems to be working for the test. Maybe it has to do with conn.response.read happening before?