`swift upload` will always display an error for non-admins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
New
|
Undecided
|
Unassigned |
Bug Description
When uploading an object, swift client will attempt to first ensure the container exists before uploading the object. This is great, and a wonderful convenience, unless you happen to be a lowly non-admin user. In that case, you get an ugly error saying you are not authorized to create the container*, but your object is successfully uploaded. This of course assumes you have been granted write access to the container.
* Which causes all kinds of confusion, because the error doesn't reflect the action the user was taking. The user was uploading an object, then all of a sudden they get an error about not being able to create a container, one that happens to already exist, and overlooking the fact the object had indeed been uploaded.
description: | updated |
I believe this is a duplicate of bug 1204558. I provided a patch to fix this, if you have a chance, feel free to review it: https:/ /review. openstack. org/#/c/ 60400/