account auto create failure does server error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Confirmed
|
Low
|
Unassigned |
Bug Description
This is maybe a pretty low priority, but when the container or account existence checks *fail* vs a "successful" 404 - the client still gets a 404. I went back pre-get_info refactor and i guess it always worked this way.
But I'm not sure that we shouldn't return a server error in this case. In the container create case getting a 404 seems a little mean to the poor client, who may still be able to perform a HEAD request on their "not yet auto created" account, but get's a 404 when they try to create a container.
A server error would indicate that they may return the request unmodified, but they should wait - or report the issue to the service provider.
You can duplicate the bug by trying to create a container with your account-server's turned off, but changing the permissions on /srv/node/
tags: | added: low-hanging-fruit |
Changed in swift: | |
importance: | Undecided → Medium |
milestone: | none → next-icehouse |
Changed in swift: | |
status: | New → Confirmed |
Changed in swift: | |
assignee: | nobody → Balazs KOSSOVICS (balazs-kossovics-ext) |
Changed in swift: | |
status: | In Progress → Confirmed |
Changed in swift: | |
milestone: | 1.13.1-rc1 → none |
Changed in swift: | |
importance: | Medium → Low |
Changed in swift: | |
assignee: | Pradeep Kumar Singh (pradeep-singh-u) → Annapoornima Koppad (annakoppad) |
Changed in swift: | |
assignee: | Annapoornima Koppad (annakoppad) → Jeevan (jeevanpuchakay) |
assignee: | Jeevan (jeevanpuchakay) → nobody |
Fix proposed to branch: master /review. openstack. org/69576
Review: https:/