Bug 994252 - Should return a more human friendly error when there is no more space on the storage device
Summary: Should return a more human friendly error when there is no more space on the ...
Keywords:
Status: NEW
Alias: None
Product: Gluster-Swift
Classification: Community
Component: object-server
Version: 1.9.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-06 21:36 UTC by Luis Pabón
Modified: 2023-01-31 23:39 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Luis Pabón 2013-08-06 21:36:26 UTC
Description of problem:
I tried verifying that I get a 507 returned, but instead I get a 503.

Setup:

    fill up /mnt/gluster-storage/test/container
    Create a 100MG file called 100m.img
    curl -v -X PUT -H 'X-Auth-Token: <you need to get your own token>' -T 100m.img http://127.0.0.1:8080/v1/AUTH_test/myfile2/a
    About to connect() to 127.0.0.1 port 8080 (#0)
    Trying 127.0.0.1...
    Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
    > PUT /v1/AUTH_test/myfile2/a HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: 127.0.0.1:8080
    > Accept: */*
    > X-Auth-Token: AUTH_tk42adf371bba74dd7a58838a77abed512
    > Content-Length: 104857600
    > Expect: 100-continue
    >
    < HTTP/1.1 100 Continue
    We are completely uploaded and fine
    < HTTP/1.1 503 Internal Server Error
    < Last-Modified: Tue, 06 Aug 2013 04:02:30 GMT
    < Content-Length: 118
    < Content-Type: text/html; charset=UTF-8
    < Date: Tue, 06 Aug 2013 04:02:30 GMT
    < 

I suggest adding a test in test/unit/proxy/test_proxy.py which mocks the open call, then sends the python command over to the server. In response it should expect a 507.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.