x-object-manifest does not work with quoted names

Bug #1070288 reported by sirkonst
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Expired
Undecided
Unassigned
python-swiftclient
Incomplete
Undecided
Unassigned
swift (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I tried upload file by segments with non-ASCII simbols in name:

$ swift -A * -U * -K * upload -S 1048576 segtest "test,\321\202\320\265\321\201\321\202"

The uploading is successful, but if I'm downloading a file, I get the file to zero size.

$ swift -A * -U * -K * download segtest "test,\321\202\320\265\321\201\321\202"

With ACSII names all OK.

Revision history for this message
sirkonst (sirkonst) wrote :

Bump!

Also is affect when in file name normal ACSII simbols and simbol ",".

Revision history for this message
Iryoung Jeong (iryoung) wrote :

Could you tell us which version of swift & what kinds of environment you use?

For my Ubuntu12.04 with current trunk swift, "," works well.

$ swift -A * -U * -K * upload segtest2 "tt,"
tt,

$ swift -A * -U * -K * download segtest2 "tt,"
tt, [headers 0.026s, total 0.027s, 0.018s MB/s]

 ls -alh "tt,"
-rw-rw-r-- 1 simple simple 483 Oct 29 23:30 tt,

no longer affects: openstack-community
Revision history for this message
sirkonst (sirkonst) wrote :

I tested in ubuntu 12.4 and swift 1.4.8 (exsex)

$ lsb_release -d
Description: Ubuntu 12.04.1 LTS
$ aptitude show swift-proxy | grep Version
Version: 1.4.8-0ubuntu2

Simple uploading work fine. This bug about segments upload, plz try upload file with size more then 10MB and option -S 1048576).

Revision history for this message
sirkonst (sirkonst) wrote :

and check file size after download.

Revision history for this message
Samuel Merritt (torgomatic) wrote :

The bug could be in one of two places: either (a) in python-swiftclient, or (b) in Swift. If you perform these operations using curl or some other plain-HTTP client, does the bug occur, or does it only happen when using python-swiftclient?

Changed in swift:
status: New → Incomplete
Changed in python-swiftclient:
status: New → Incomplete
Revision history for this message
Iryoung Jeong (iryoung) wrote :

$ swift -A * -U * -K * upload -S 100 segtest2 "tt,"
tt, segment 2
tt, segment 1
tt, segment 0
tt, segment 4
tt, segment 3
tt,
$ rm tt,
$ swift -A * -U * -K * download segtest2 "tt,"
tt, [headers 0.069s, total 0.070s, 0.007s MB/s]
$ ls -alh tt,
-rw-rw-r-- 1 simple simple 483 Oct 29 23:30 tt,

So, with current master of both python-swiftclient & swift, it works normally for me.

Can you try this with lastest master?

(and for me, non-ascii segemented up/download works well either )

I'd looked up old bugs & and found https://bugs.launchpad.net/python-swiftclient/+bug/1008940/comments/11 may be related. The comment didn't specify exact bug, but commenter said the issue was solved some months ago.

Revision history for this message
sirkonst (sirkonst) wrote :

@iryoung, are you confirm the problem on ubuntu versions packages or not? I did not try lastest master, yet.

@torgomatic, primary the bug affects swift-proxy, and because it swiftclient does not working correctly with segments (with special files names).

I wrote test for it - https://gist.github.com/3985874

Revision history for this message
sirkonst (sirkonst) wrote :

Bump.

Chuck Short (zulcss)
Changed in swift (Ubuntu):
status: New → Incomplete
Revision history for this message
sirkonst (sirkonst) wrote :

Bump!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for swift (Ubuntu) because there has been no activity for 60 days.]

Changed in swift (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Object Storage (swift) because there has been no activity for 60 days.]

Changed in swift:
status: Incomplete → Expired
Revision history for this message
Chmouel Boudjnah (chmouel) wrote :

I think this was addressed by https://review.openstack.org/#/c/21907/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.