Error in unit tests, when xattr have length more than 254.
Bug #1079131 reported by
Vladimir Vechkanov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Vladimir Vechkanov |
Bug Description
Unit tests for object-server. For example such tests as "test_PUT_
The reason is that swift writes pikled xattr in parts, 254 bytes each. So while reading it we should concatenate several parts. But unit test just read only first part and try to unpikle it. It works while xattrs were less than 254 bits, but when they are longer it causes the error.
Changed in swift: | |
assignee: | nobody → Vladimir Vechkanov (vvechkanov) |
Changed in swift: | |
assignee: | Vladimir Vechkanov (vvechkanov) → nobody |
Changed in swift: | |
importance: | Undecided → Low |
Changed in swift: | |
status: | New → Triaged |
Changed in swift: | |
assignee: | nobody → Vladimir Vechkanov (vvechkanov) |
Changed in swift: | |
milestone: | none → 1.9.0 |
Changed in swift: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
So is there some condition under which those unit tests fail? I mean, if the test is always putting in a small enough amount of metadata that it all fits in one attribute, and then only pulling out one attribute, then what's the problem?